* After the completion of maven-release-plugin, run ** the reincrementalify goal ** commit POM changes as new commit ** Do another push to SCM
Everything can be implemented as a single Maven Mojo (e.g. "incrementals-release")
There is a risk of some edge cases, but it would help plugin developers a lot to keep their master branches release-ready at any time. It's also important for all CD-alike flows which may break if they do not reincrementalify.
There is a risk of some edge cases, but it would help plugin developers a lot to keep their master branches release-ready at any time. It's also important for all CD-alike flows which may break if they do not reincrementalify.
{{`completionGoals` avoids the extra commit and push and makes it part of the `}}[maven-release-plugin] prepare for next development iteration` which seems like the best of both worlds :)
{{`completionGoals` avoids the extra commit and push and makes it part of the `}}[maven-release-plugin] prepare for next development iteration{{` step}}
{{`completionGoals` avoids the extra commit and push and makes it part of the `}}[maven-release-plugin] prepare for next development iteration` commit which seems like the best of both worlds :)
All PRs now merged. I am not inclined to bother trying to consume the jenkinsci/pom update yet, as it should have no practical impact (only jenkinsci/jenkins is incrementalified using it, and Kohsuke Kawaguchi already runs reincrementalification in his release script); the important part was to get a plugin-pom release cut which uses it, and that has happened.