[
http://jira.codehaus.org/browse/MNG-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raffaele Verre reopened MNG-4899:
---------------------------------
Sorry
David Julian says:
"
Maven recognizes versions that match the following pattern:
A.B.C-D or A.B.C-foo
where:
A is the Major Version,
B is the Minor Version,
C is the Incremental Version (also known as Bug Fix),
D is the Build Number, and
'foo' is the Qualifier.
A, B, C, and D, are compared numerically and the qualifier is a string
compare.
A version may only have a build number or a qualifier, not both.
The numbers are considered zero if not present i.e., 1.1 is the same as
1.1.0 and 1.1-0.
"
in http://docs.codehaus.org/display/MAVEN/Versioning:
" 1.0-alpha-10 ==? 1.0-alpha-2: 10 > 2, so '1.0-alpha-10' is newer"
1.0 and 1.0.0 for Maven are the same so 1.0.0-alpha-10 is newer than
1.0.0-alpha-2
so I don't understand why I have this error:
Couldn't find a version in [2.0.0-alpha-14, 2.0.0-alpha-15, 2.0.0-alpha-16] to
match range [2.0.0-alpha-1,)
Why 2.0.0-alpha-16 is not newer than 2.0.0-alpha-1?
> strange behavior during the dependency resolution
> -------------------------------------------------
>
> Key: MNG-4899
> URL: http://jira.codehaus.org/browse/MNG-4899
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Reporter: Raffaele Verre
> Assignee: Benjamin Bentmann
>
> Running mvn compile I have this error:
> Couldn't find a version in [2.0.0-alpha-14, 2.0.0-alpha-15, 2.0.0-alpha-16]
> to match range [2.0.0-alpha-1,)
> Is correct? Look strange for me....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
