|
||||||||||||||
|
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-230) display-*-update... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-230) display-*-u... SebbASF (JIRA)

These are valid version numbers. There are projects that use yyyymmdd.hhmmss as their version numbers... yes it is an asinine and stupid scheme... yes it causes sequencing issues when comparing with less stupid schemes... but it is valid... if you change your version numbering scheme, you are supposed to change Group Id and/or Artifact Id... this plugin will not legislate for user error.
If you don't want to see those versions you configure a rules.xml with
<ignoreVersion type="regex">\d{8}\.\d{6}</ignoreVersion>