Skip to content

Conversation

@michaelsonnleitner
Copy link
Contributor

adds feature #1340

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@michaelsonnleitner
Copy link
Contributor Author

@ricardozanini have a look at it. of couse i will add docu for it if its is ok in your opinion.

@michaelsonnleitner michaelsonnleitner marked this pull request as ready for review October 23, 2025 17:40
@michaelsonnleitner michaelsonnleitner requested a review from a team as a code owner October 23, 2025 17:40
@michaelsonnleitner michaelsonnleitner marked this pull request as draft October 23, 2025 17:40
@ricardozanini
Copy link
Member

Can you also please take a look on the CI?

@michaelsonnleitner michaelsonnleitner marked this pull request as ready for review October 24, 2025 11:39
…spec mapping to ensure that config key is right
@michaelsonnleitner

This comment was marked as resolved.

@michaelsonnleitner

This comment was marked as resolved.

Copy link
Member

@ricardozanini ricardozanini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! Do you need a minor release?

@ricardozanini
Copy link
Member

@mcruzdev @hbelmiro I wouldn't mind a pair of fresh eyes on this.

@michaelsonnleitner
Copy link
Contributor Author

Great work! Do you need a minor release?

thank you 😃
not now.

should i raise another feature req. for addjng the JarGavCoordinateReader? i dont want to add it to this one. maybe i have some time in the next weeks...

@ricardozanini
Copy link
Member

should i raise another feature req. for addjng the JarGavCoordinateReader? i dont want to add it to this one. maybe i have some time in the next weeks...

Please do! You can open an issue and implement it once you have the time ;)

@michaelsonnleitner
Copy link
Contributor Author

michaelsonnleitner commented Nov 3, 2025

@ricardozanini when do you plan releasing it?

@ricardozanini
Copy link
Member

@ricardozanini when do you plan releasing it?

Once we have a meaningful pack of PRs merged. I think we can release one patch version this week.

@ricardozanini ricardozanini merged commit 63315ab into quarkiverse:main Nov 4, 2025
11 checks passed
github-actions bot pushed a commit that referenced this pull request Nov 4, 2025
* Support GAV coordinates for client generation #1340

* Support GAV coordinates for client generation #1340

* avoid star imports

* SUPPORTED_EXTENSIONS refactored for better use

* add filter for artifactIds & improved config naming(singular/plural) & tests simplicity & add config options to GlobalCodegenConfig

* windows problem with colon in filename & extended test with specific spec mapping to ensure that config key is right

* use verify phase to store artifacts to local mvn repo to get website / codeql action green

* renaming and javadoc

* use package phase for artifact installation to get codeql action running

---------

Co-authored-by: Michael Sonnleitner <[email protected]>
ricardozanini added a commit that referenced this pull request Nov 4, 2025
* Support GAV coordinates for client generation #1340 (#1343)

* Support GAV coordinates for client generation #1340

* Support GAV coordinates for client generation #1340

* avoid star imports

* SUPPORTED_EXTENSIONS refactored for better use

* add filter for artifactIds & improved config naming(singular/plural) & tests simplicity & add config options to GlobalCodegenConfig

* windows problem with colon in filename & extended test with specific spec mapping to ensure that config key is right

* use verify phase to store artifacts to local mvn repo to get website / codeql action green

* renaming and javadoc

* use package phase for artifact installation to get codeql action running

---------

Co-authored-by: Michael Sonnleitner <[email protected]>

* Apply suggestion from @ricardozanini

* Apply suggestion from @ricardozanini

---------

Co-authored-by: Michael Sonnleitner <[email protected]>
Co-authored-by: Michael Sonnleitner <[email protected]>
Co-authored-by: Ricardo Zanini <[email protected]>
@ricardozanini ricardozanini linked an issue Nov 5, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support GAV coordinates for "input-base-dir"

3 participants