Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #11953
Closed
Open
Issue created Mar 23, 2022 by Administrator@rootContributor

[REQ] Allow selection of MP REST API version for MicroProfile REST client generation

Created by: tjquinno

Is your feature request related to a problem? Please describe.

The current support for generating MicroProfile REST client artifacts generates a dependency on MP REST client version 1.4.1 in the pom.xml. There have been releases of 2.0 (Dec. 2020) and 3.0 (Dec. 2021) since this generator was first added.

Describe the solution you'd like

Users could select to generate code that would use either MP REST API 1.4.1 or 2.0 or 3.0.

Describe alternatives you've considered

Users can hand-edit the code from the current generator. To use MP REST API 2.0 this requires only updating the version in the dependency declaration in the pom.xml file.

For 3.0, though, the manual changes needed are not just changing the version in the pom but also changing Java packages from javax... to jakarta... in the generated Java code, a much more tedious process.

Additional context

There are no feature changes in MP REST API from 1.4.1 to 2.0 to 3.0, only the changes outlined above. The resulting updates to the generator to handle versions 2.0 and 3.0 should be relatively straightforward.

It might be feasible to retire support for 1.4.1, given the age of that release, but because of the very small difference in the templating for 1.4.1 vs. 2.0 (one line in the pom.xml template) it seems to be quite straightforward to keep support for that release in the generator. Perhaps the default version should be a later release than 1.4.1, though.

The Helidon team is very interested in contributing this enhancement.

Assignee
Assign to
Time tracking