[
http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229458#action_229458
]
Bob Fields commented on MNG-3518:
---------------------------------
Still broken in 2.2.1. Worse yet, it's completely broken for four part
identifiers (used by Spring, Hibernate, and Eclipse Helios/OSGi), no versions
are ever selected. See http://forum.springsource.org/showthread.php?t=88779.
Also the error I am experiencing:
Couldn't find a version in [3.6.0.v20100517, 3.2.0-v20060601] to match range
[3.5.0,4.0.0)
3.6.0.anything (or 3.5.0.anything) should always be seen as later than 3.5.0.
I don't really see how adding the -v date identification would have broken
existing users, but I guess it's a moot point.
I verified this issue is fixed in maven3 beta, I hope it's released soon.
> Handle date qualifier in DefaultArtifactVersion
> -----------------------------------------------
>
> Key: MNG-3518
> URL: http://jira.codehaus.org/browse/MNG-3518
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.9
> Reporter: Vincent Siveton
> Fix For: 3.x / Backlog
>
> Attachments: DefaultArtifactVersion-handledate.diff, pom.xml
>
>
> Eclipse artifacts use a date pattern in version qualifier and build fail with
> the following error
> {noformat}
> [INFO] Failed to resolve artifact.
> Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0)
> org.eclipse.equinox:app:jar:null
> {noformat}
> The following patch adds javadoc for compareTo() to be more clear.
> Also, it handles date pattern in the version to allow "1.0.0" <
> "1.0.0-v20070606". Internally, it compares "1.0.0-19068845215" (ie new
> Date(Integer.MAX_VALUE, 12, 31 )) to "1.0.0-20070606"
--
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
