Repository navigation
(2.0.x) Backport MODCLUSTER-859 Upgrade jboss-parent and upgrade to new Nexus release process and MODCLUSTER-878 Update pom to be compliant with Maven Central - #1009
Merged
Conversation
(cherry picked from commit cb3539b) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…on module (cherry picked from commit 2c5ccf0) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…ns synchronized. For that matter never publish this module via Maven during deploy. (cherry picked from commit 347ec21) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
Squashes the following upstream commits: - 697ff7f Build(deps): Bump org.jboss:jboss-parent from 41 to 43 - 0f1c077 Build(deps): Bump org.jboss:jboss-parent from 43 to 44 - 8d0b6a0 Build(deps): Bump org.jboss:jboss-parent from 44 to 46 - 206c7a5 Build(deps): Bump org.jboss:jboss-parent from 46 to 47 - 14b123c Build(deps): Bump org.jboss:jboss-parent from 47 to 48 - 0ed1a41 Build(deps): Bump org.jboss:jboss-parent from 48 to 49 - e3fa08e Build(deps): Bump org.jboss:jboss-parent from 50 to 51 - f34892c Build(deps): Bump org.jboss:jboss-parent from 53 to 54 including the parent version changes of MODCLUSTER-859 (49e9da5, to 50) and MODCLUSTER-867 (4a08f64, to 53). The Checkstyle version pin from MODCLUSTER-867 (4a08f64) is included as well, since Checkstyle managed by jboss-parent 54 requires JDK 21 while 2.0.x still builds on JDK 11 and 17; 10.26.1 is the latest version running on JDK 11. The rest of MODCLUSTER-867 (Java SE 17 as the minimum) does not apply to 2.0.x. Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…ss-parent. (cherry picked from commit 85f9474) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…lease process 2.0.x backport: 2.0.x has no BOM, so the project metadata and the Nexus staging properties are kept in the root POM. The parent upgrade itself is part of the squashed jboss-parent 41 to 54 bump. Signed-off-by: Radoslav Husar <radosoft@gmail.com> (cherry picked from commit 49e9da5) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…ents - Skip staging of the code-coverage module via nexus.skipPublishing. - Declare a description in all POMs, including the root one which lost it when the project metadata moved to the BOM. - Skip tests in both release:prepare and release:perform builds. - Temporarily keep SCM changes manual (no push, local checkout) until the new release infrastructure is tested. - Remove the obsolete staging repository comment from the BOM. 2.0.x backport: 2.0.x has no BOM, so the properties go to the root POM; there is no Tomcat 11.0 module, a description is added to the Tomcat 8.5 module instead. Signed-off-by: Radoslav Husar <rhusar@ibm.com> (cherry picked from commit 32a5c69) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
The module was only added by the coverage and jboss-release profiles, so a plain release:prepare did not update its version, leaving the tag and the next development iteration with a stale parent version. Make it a regular module instead; it is never deployed, and without JaCoCo execution data the aggregate report is empty. Signed-off-by: Radoslav Husar <rhusar@ibm.com> (cherry picked from commit 38ee966) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
2.0.x backport: Adapted for the 2.0.x branch, which has no BOM. Signed-off-by: Radoslav Husar <rhusar@ibm.com> (cherry picked from commit c393e5a) Signed-off-by: Radoslav Husar <rhusar@ibm.com>
…ly distribution. Signed-off-by: Radoslav Husar <rhusar@ibm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://redhat.atlassian.net/browse/MODCLUSTER-811
https://redhat.atlassian.net/browse/MODCLUSTER-878
https://redhat.atlassian.net/browse/MODCLUSTER-859
https://redhat.atlassian.net/browse/MODCLUSTER-814