[jira] Updated: (MNG-3518) Handle date qualifier in DefaultArtifactVersion

["Vincent Siveton (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton updated MNG-3518:
---------------------------------

    Attachment: pom.xml

Dummy Pom which produces errors:

{noformat}
[INFO] Failed to resolve artifact.

Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
  org.eclipse.equinox:app:jar:null

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
{noformat}

> Handle date qualifier in DefaultArtifactVersion
> -----------------------------------------------
>
>                 Key: MNG-3518
>                 URL: http://jira.codehaus.org/browse/MNG-3518
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.9
>            Reporter: Vincent Siveton
>         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