gaul
Q: How do you release?
Asking, as https://github.com/gaul/modernizer-maven-plugin/blob/8ddb06e85d9aa4cdb45504f937d6d4f9ec15d57d/pom.xml#L13 (current master!) still shows version 2.9.0! This means if anyone rebuilds locally, will replace the release downloaded from Maven Central.
Looks like I missed a step! I manually run these commands for every release:
git rebase upstream/master
mvn versions:set -DnewVersion=1.2.2
git add -p
git commit -m 'modernizer-maven-plugin 1.2.2 release'
\mvn clean deploy -P release
git tag -a modernizer-maven-plugin-1.2.2 -m 'modernizer-maven-plugin 1.2.2 release'
mvn versions:set -DnewVersion=1.3.0-SNAPSHOT
git add -p
git commit -m 'Bump to 1.3.0-SNAPSHOT'
git push upstream master
git push upstream --tags
I haven't changed this process in 10 years -- is there a better way?
No, this is good. I was curious in several things:
- do you use maven-release-plugin (nope)
- do you use nexus-staging-maven-plugin (nope: good, that POS should be ditched from the build)
- these two things I wanted to know to continue on "cleanup" trail, as next is removal of parent POM from 2011 and now as I got info I wanted, removal of nx staging plugin as well.
@cstamas any other cleanups we could make here? I would like to make a new release soon.
Nope, all looks good, thanks! Parent and staging plugin are gone, that was my goal.