Tie versioning to a Maven Release version policy #73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
magnusp
force-pushed
the
changeset-version-policy
branch
from
573fac0 to
5059eed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a ChangesetsVersionPolicy that can be used with Maven Release to set and progress versions as part of the release executions. The change maintains backward compatability, where a flag
useReleasePluginIntegrationsignals that changesets should only do changeset processing (+ bump VERSION file). In cases where a branch is used to prepare a release the goal execution would bechangesets:prepare release:prepare- one added benefit is that Maven Release will correctly tag a commit and push that tag to the branch. The actual release can then be pointed to by tag instead of a commit reference or HEAD.