[
http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204641#action_204641
]
Brett Porter commented on MNG-3518:
-----------------------------------
at this stage we don't look to be doing any further feature releases for 2.x.
Aside from bugfix releases, the next release will be 3.0. Ranges need a more
comprehensive look than tacking on workarounds like this anyway - the patch
will break compatibility for someone and need to be handled appropriately.
> 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
>
> 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
