Details
Improvement
Closed
Major
Description
Our current release process is long and error prone.
Ideally we should avoid multiple builds forced by the mvn release:perform and do by hand the same things, just
in a smarter way. Something like clean up your repo, perform a full build, tag, change poms in tag, build again
with a new clean repo, deploy, assembly, javadoc and upload, so that we only have two builds around, and skip
tests on operations such as assembly.
It would also be nice to have an utility to send the same message to all the publishing sources (using javamail
and http support it can be coded if one has time, but testing it can be really annoying...)
Many of the points raised are addressed (such as skipping tests after the initial extensive tests); the only outright pain is testing the resulting archive; and we have had some luck asking members on the development list to perform this step.