|
||||||||||||||
|
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-238) Older version f... Jean-Pierre Froud (JIRA)
- [mojo-dev] [jira] (MVERSIONS-238) Older vers... Jean-Pierre Froud (JIRA)
- [mojo-dev] [jira] (MVERSIONS-238) Older vers... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-238) Older vers... Jean-Pierre Froud (JIRA)
- [mojo-dev] [jira] (MVERSIONS-238) Older vers... Stephen Connolly (JIRA)

Maven default versions have some strange rules.
If a version number has three segments and all those segments are numbers and there are no leading zeros, then the versions will be compared segment by segment. If there are leading zeros in any segment then the whole version is treated as a string. If you are comparing a segment version with a string version then string versions are always older.
This is insane... it is also core Maven functionality, which the versions-maven-plugin just reflects for you.
Thus