8000 Stop using jboss-parent by Pepo48 · Pull Request #46241 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Stop using jboss-parent - #46241

Merged
vmuzikar merged 2 commits into
keycloak:mainfrom
Pepo48:issue-40125
May 6, 2026
Merged

vmuzikar merged 2 commits into
keycloak:mainfrom
Pepo48:issue-40125

Conversation

@Pepo48
@Pepo48 Pepo48 commented Feb 11, 2026
Copy link
Copy Markdown
Contributor

Closes: #40125

@vmuzikar
Copy link
Copy Markdown
Contributor

@stianst @ASzc @drichtarik Does this work for you?

@drichtarik
drichtarik commented Feb 17, 2026 •
Copy link
Copy Markdown
Contributor

We are running test builds and adding dependencies/plugins that are missing. This is going to take a couple of days but it's included in the upcoming sprint as our goal

@stianst stianst left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is not going to work for the release; we're relying on a few bits and pieces from jboss-parent there. Need to look into exactly what, but don't have time right now.

Comment thread quarkus/tests/integration/pom.xml Resolved
@stianst stianst self-assigned this Feb 18, 2026
@Pepo48
Pepo48 commented Feb 18, 2026
Copy link
Copy Markdown
Contributor Author

@stianst sorry for dragging you into this again, I hadn’t noticed that you were tagged. I’ve already discussed it with Denis and as he mentioned above, they’re currently looking into what needs to be done from the downstream perspective. Once they finish, I’ll be ready to use the testing org to verify whether anything else needs to be adjusted to fix the release workflows at that level as well.

@pskopek
pskopek commented Mar 2, 2026
Copy link
Copy Markdown
Contributor

The latest changes successfully tested on keycloak-rel-testing org.
https://github.com/keycloak-rel-testing/keycloak-rel/actions/runs/22576229928

@pskopek pskopek left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!

@stianst
stianst commented Mar 2, 2026
Copy link
Copy Markdown
Contributor

The latest changes successfully tested on keycloak-rel-testing org. https://github.com/keycloak-rel-testing/keycloak-rel/actions/runs/22576229928

I'm surprised - was really certain gpg or something around repo config wouldn't be right.

I'll take a look at this next week just to make double sure; as I really don't want to fight issues around this when we do the 26.6 release ;)

@stianst
stianst force-pushed the issue-40125 branch 2 times, most recently from 8be258a to b11f15d Compare March 3, 2026 08:50
@stianst stianst added this to the 26.7.0 milestone May 4, 2026
@Pepo48
Pepo48 marked this pull request as ready for review May 4, 2026 09:48
@Pepo48
Pepo48 requested review from a team as code owners May 4, 2026 09:48
Pepo48 and others added 2 commits May 4, 2026 11:48
Closes: keycloak#40125

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
Should match the versions from jboss-parent to
prevent conflicting versions.

Signed-off-by: Badiuzzaman Iskhandar <badiskhand@ibm.com>
Comment thread pom.xml
<maven-assembly-plugin.version>3.1.1</maven-assembly-plugin.version>
<maven-deploy-plugin.version>2.8.2</maven-deploy-plugin.version>
<maven-jar-plugin.version>3.5.0</maven-jar-plugin.version>
<maven-compiler-plugin.version>3.13.0</maven-compiler-plugin.version>
@michalvavrik michalvavrik May 4, 2026 •
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Quarkus is using maven-compiler 3.15.0, while you picked 3.13.0. Is this in order to align with Maven core and other plugins? Because only information in your PR / commits I found was "Should match the versions from jboss-parent to prevent conflicting versions." which does not add up, because JBoss Parent version 39 currently uses 3.8.1.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@drichtarik this got postponed a bit and now it's ready to be merged. Should we keep these versions as they are or should we bump some of them? Thanks!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

For product all we're trying to establish with the introduction of these lines, is to ensure that these plugin versions are defined. Removing jboss-parent otherwise allows them to float, which causes problems.

3.13 vs 3.15, I don't think it would matter, but we'd need to do more trial builds to confirm

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

3.13 vs 3.15, I don't think it would matter, but we'd need to do more trial builds to confirm

FWIW the only reason why I was commenting here was because I tried to use annotationProcessorPathsUseDepMgmt which was introduced in 3.12. I am fine with 3.13, but it seems random and I think explanation on why these exact plugin versions were picked is missing. As long as there is a reason, np.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'll check with the team

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We could perhaps split the two things; since we've tested this PR both for upstream and downstream releases we can keep it as is, then plan to upgrade plugins as a follow-up?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I agree.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes. This one has been open for a long time. If you want to merge this PR as is or with 3.15, that's fine. As long as there is a dependency definition in the keycloak POMs, we can override the version at product build time if it breaks something, upstreaming fixes as appropriate.

@vmuzikar vmuzikar left a comment •
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@Pepo48 Sorry if I missed this in the discussion but why were the test changes needed?

@Pepo48
Pepo48 commented May 6, 2026
Copy link
Copy Markdown
Contributor Author

@Pepo48 Sorry if I missed this in the discussion but why were the test changes needed?

Because of a surefire plugin config change, see #45616 (comment) (the paragraph about the test changes)

@vmuzikar vmuzikar left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Because of a surefire plugin config change, see #45616 (comment) (the paragraph about the test changes)

Right, I forgot about that. Thanks, LGTM.

@vmuzikar
vmuzikar merged commit f20005b into keycloak:main May 6, 2026
90 checks passed
@stianst stianst mentioned this pull request Jun 1, 2026
sashyo pushed a commit to tide-foundation/keycloak-IGA that referenced this pull request Jul 20, 2026
* Stop using jboss-parent

Closes: keycloak#40125

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>

* Add Maven plugins version from jboss-parent

Should match the versions from jboss-parent to
prevent conflicting versions.

Signed-off-by: Badiuzzaman Iskhandar <badiskhand@ibm.com>

---------

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
Signed-off-by: Badiuzzaman Iskhandar <badiskhand@ibm.com>
Co-authored-by: Badiuzzaman Iskhandar <badiskhand@ibm.com>
@stianst stianst mentioned this pull request Sep 1, 2026
1 of 2 tasks
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.

Stop using jboss-parent

8 participants

0