I suggest going the Maven Way, always working with snapshots during development, i.e. currently it would be 2.7.4-SNAPSHOT, then build a single commit with whatever milestone, release candidate or release we are going to release, tag that commit and switch directly to the next snapshot (or snapshots, in case there are multiple branches for new development and maintenance). If we want to do that manually with Versions Maven Plugin [1] with
# Set release version in all POMs mvn versions:set -DnewVersion=2.7.4 # Verify if the POM changes are OK, then remove the POM backup files mvn versions:commit # Build, commit, deploy (Maven Central) and tag release ... # Set next snapshot mvn versions:set -DnewVersion=2.7.5-SNAPSHOT && mvn versions:commit or using Maven Release Plugin via release:prepare, release:perform etc., see [2], is debatable. The way we deploy to Maven Central or snapshot repositories is also an open question, nothing is prepared in the POMs for that, just like for the release process. E.g.,deployment + manual build promotion to Central via Website are possible usinf Maven Deploy and the Sonatype Nexus website, but also Nexus Staging Maven Plugin [4], by means of which it is also possible to promote the build to Central right from the Maven command line [4]. I know how to do all that. The open question is whether we add that before or after the cutover. Same question about GPG Maven Plugin [5] for signing artifacts, distribution management settings (release and snapshot repositories to deploy to) in the POM etc. If a release is not imminent after the cutover and it is just about everyone now building with Maven instead of Ant, it can be done later. If the goal is to release immediately, it should be done before. [1] https://www.mojohaus.org/versions/versions-maven-plugin/index.html [2] https://maven.apache.org/maven-release/maven-release-plugin/ [3] https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/maven-plugin/README.md [4] https://help.sonatype.com/repomanager2/staging-releases/configuring-your-project-for-deployment [5] https://maven.apache.org/plugins/maven-gpg-plugin/ There is more, but I leave it at that for this message. Regards -- Alexander Kriegisch https://scrum-master.de Mukul Gandhi schrieb am 21.12.2023 21:08 (GMT +07:00): > I'm not sure. But maybe, can we try making a XalanJ 2.7.4 (is this > XalanJ version number for the next release ok?) maven release from the > dev repos branch xalan-java-mvn-refactored? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
