As my daily work I contribute few bug fixes to jenkins plugins and officially maintain some of them, so have to run the release process so a new version is available in Jenkins update-center and my customer can get the fix.
maven-release-plugin rely on maven scm adaptor fir git command line client, and there's some odd incompatibility with recent git releases, so if you don't run "latest" you end up with some broken release. What I used to see is release tag created and pushed to origin, but no release commit.
The option I used to apply to fix this with the plugins I maintain was to force the release plugin version in pom.xml. Anyway this doesn't make much sense imho to pollute the pom with such a local issue.
Took me a while, but I re-discovered I can just force the plugin version to be used by passing the full GAV to maven command line :
This is a tip I should include in my book ...
maven-release-plugin rely on maven scm adaptor fir git command line client, and there's some odd incompatibility with recent git releases, so if you don't run "latest" you end up with some broken release. What I used to see is release tag created and pushed to origin, but no release commit.
The option I used to apply to fix this with the plugins I maintain was to force the release plugin version in pom.xml. Anyway this doesn't make much sense imho to pollute the pom with such a local issue.
Took me a while, but I re-discovered I can just force the plugin version to be used by passing the full GAV to maven command line :
mvn org.apache.maven.plugins:maven-release-plugin:2.5:release:prepare mvn org.apache.maven.plugins:maven-release-plugin:2.5:release:perform
This is a tip I should include in my book ...
0 commentaires:
Enregistrer un commentaire