|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MVERSIONS-214) support semantic... Andrei Pozolotin (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Tuomas Kiviaho (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Tuomas Kiviaho (JIRA)
- [mojo-dev] [jira] (MVERSIONS-214) support sem... Stephen Connolly (JIRA)

Before voting, I'd like a bit clarification what the actual aim is. Here are my thoughts
Verify I guess is a soft of duplication of what semver.org's enforcer-rule does, but could update be part of of already existing goals. If I understood correctly, one use case is to preserve right hand side of version range and raise only the left hand side which perhaps use-next-releases/snapshots/versions suits well. Raising both sides would then use-latest-releases/snapshots/versions. A flag such as preserveRanges could be included in order to avoid introduction of new set of goals. This flag could be applied for some of the remaining goals such as use-release and update-property/properties.
There are other versioning schemes than semantic versioning and mojo already supports version number rules to have some sort of control over what's going on. A comparison rule for semantic versions (semver as basis perhaps) solve this.