-
Story
-
Resolution: Fixed
-
Minor
-
None
If you have opted into Incrementals, is it still possible to run maven-release-plugin or does it get too confused?
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-51658 Plugin POM should automatically run reincrementalify after the release
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-50693] Script to interoperate with maven-release-plugin
If interoperability with MRP is necessary, which it surely will be for Jenkins core at least, then perhaps we need to have a tool to fix up the POM after a release as in JENKINS-50699 and require that to be run.
Experimented further with a multimodule test repository using profiles and other setup matching what is proposed for Incrementals. Again after using MRP, POMs are reset to using literal versions, so subsequent mvn clean deploy -Dset.changelist commands simply deploy timestamped snapshots to the regular snapshot repository, until you reincrementalify the repo like this.
Another option for a plugin developer is of course to manually git tag and mvn deploy -Dchangelist= releases, though this is more cumbersome and error-prone than using MRP.
mvn help:evaluate -Dexpression=project.version -Doutput=version && mvn versions:set -Ddollar='$' -DnewVersion='${dollar}{revision}${dollar}{changelist}' -DgenerateBackupPoms=false && mvn versions:set-property -Dproperty=revision -DnewVersion=`sed -e 's/-SNAPSHOT$//' < version` -DgenerateBackupPoms=false && rm version
Formally documented this script. Can promote it to a saved file somewhere later, TBD.
Will need to have a repository of related scripts anyway, so may as well do this one.
It gets somewhat confused. As seen here, the right version is actually released, but the “next development iteration” is not configured correctly and would require manual cleanup before again being ready for publishing to Incrementals.