From 70f34212f19d1090d9b2a65e3be639070725d6a0 Mon Sep 17 00:00:00 2001 From: Brian Stansberry Date: Sat, 30 Aug 2025 12:06:24 -0400 Subject: [PATCH] [JBMETA-466] Update to JBoss Parent 50 and use the updated JBoss Nexus deployment process --- README.md | 98 +++++++++++++++++++++++++++++++++++++------- build-config/pom.xml | 59 +++++++++++++++++++++++++- pom.xml | 32 +++++++++++---- 3 files changed, 163 insertions(+), 26 deletions(-) diff --git a/README.md b/README.md index 88739fc8..c93c122c 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,9 @@ -Metadata data for WildFly. -======================== +# Deployment Descriptor Metadata for WildFly -This library is in charge in parsing JakartaEE descriptors and Wildfly extensions. +This library is used for parsing Jakarta EE and WildFly-specific deployment descriptor files to them and creating a Java object model representation of their content. -Building -------------------- +# Building Prerequisites: @@ -18,17 +16,87 @@ To build with your own Maven installation: mvn install -Releasing -------------------- +# Releasing -To release -``` -mvn release:prepare -Prelease -mvn release:perform -Prelease -``` +To release JBoss Metadata first checkout the project and ensure you are on the latest commit for the `main` branch with no local changes. -Don't forget to put Final in the release tag name. +Prior to releasing you should ensure you have your own GPG signing key set up, published to a key server and listed on [wildfly.org](https://www.wildfly.org/contributors/pgp/). + +## Prepare the release + +Execute: + + mvn release:prepare -Pjboss-release + +Enter the version being released: + + What is the release version for "JBoss Metadata"? (metadata) 17.0.0: 17.0.0.Final + +Don't forget to put the qualifier (e.g. Final) in the release tag name. + +The tag will default to the version: + + What is the SCM release tag or label for "JBoss Metadata"? (metadata) 17.0.0.Final: + +Set the next version: + + What is the new development version for "JBoss Metadta"? (metadata) 17.0.1.Alpha1-SNAPSHOT: 17.0.1-SNAPSHOT + +The release commit can be checked with: + + git show ${TAG} + +If everything is Ok perform the release which will deploy to Nexus. + +## Perform the release + +Execute: + + mvn release:perform -Pjboss-release + +This will deploy the release to the `wildfly-staging` repository. + +Wait for 10 minutes then visit the Validation task for the `wildfly-staging` repository in Nexus. If this task ran at least 10 minutes after the release was deployed check the latest results on the Settings tab and verify that at least one component was processed and that there were no errors. If the task has not run it can be manually kicked off using the Run button. + +e.g. + +> Processed 9 components. +> - no errors were found. +> - the deployment was a dry run (no actual publishing). + +If others are also deploying at the same time this count could be higher, the important check is that the scan was at least 10 minutes after it was deployed, 9 or more components were scanned and no errors specific to JBoss Metadata are reported. + +## Complete the release + +If no issues are reported complete the release. + +Move the component to the `releases` repository: + + git checkout ${TAG} + mvn nxrm3:staging-move + git checkout main + +Push the branch and tag to GitHub: + + git push upstream main + git push upstream ${TAG} + +## Rollback the Release + +If the release failed, revert the release. + +Delete the component from Nexus: + + git checkout ${TAG} + mvn nxrm3:staging-delete + git checkout main + +Reset your local Git checkout: + + git reset --hard upstream/main + git tag --delete ${TAG} + + +# License -License -------- * [Apache License Version 2.0](https://www.apache.org/licenses/LICENSE-2.0) \ No newline at end of file diff --git a/build-config/pom.xml b/build-config/pom.xml index e0ce211b..000159ec 100644 --- a/build-config/pom.xml +++ b/build-config/pom.xml @@ -10,11 +10,66 @@ org.jboss jboss-parent - 48 + 50 org.jboss.metadata metadata-build-config - Metadata Build Configuration 17.0.0-SNAPSHOT + + Metadata Build Configuration + Checkstyle configuration for JBoss Metadata + https://github.com/wildfly/metadata + + + + Apache License 2.0 + http://repository.jboss.org/licenses/apache-2.0.txt + repo + + + + + scm:git:git@github.com:wildfly/metadata.git + scm:git:git@github.com:wildfly/metadata.git + https://github.com/wildfly/metadata + + + + + wildfly.org + WildFly Community + wildfly.org + http://wildfly.org + + + + + + wildfly-staging + jboss-metadata-${project.version} + + + + + + + org.apache.maven.plugins + maven-jar-plugin + + + empty-javadoc-jar + package + + jar + + + javadoc + ${project.basedir}/javadoc + + + + + + diff --git a/pom.xml b/pom.xml index 5938c9e2..79e36a75 100644 --- a/pom.xml +++ b/pom.xml @@ -11,7 +11,7 @@ org.jboss jboss-parent - 48 + 50 org.jboss.metadata @@ -19,7 +19,8 @@ 17.0.0-SNAPSHOT JBoss Application Server: Metadata Aggregator - JBoss Application Server: Metadata Aggregator + WildFly: Jakarta EE Metadata Aggregator + https://github.com/wildfly/metadata pom @@ -31,6 +32,22 @@ + + scm:git:git@github.com:wildfly/metadata.git + scm:git:git@github.com:wildfly/metadata.git + https://github.com/wildfly/metadata + HEAD + + + + + wildfly.org + WildFly Community + wildfly.org + http://wildfly.org + + + org.hibernate.javax.persistence hibernate-jpa-2.1-api @@ -39,6 +56,10 @@ 3.6.0 + + wildfly-staging + jboss-metadata-${project.version} + 3.5.0.Final 4.13.2 @@ -372,11 +393,4 @@ - - scm:git:git@github.com:jboss/metadata.git - scm:git:git@github.com:jboss/metadata.git - scm:git:git@github.com:jboss/metadata.git - HEAD - -