You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2008/04/13 16:19:58 UTC
[jira] Created: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
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
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
[jira] Issue Comment Edited: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Johan Walles (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204594#action_204594 ]
Johan Walles edited comment on MNG-3518 at 12/30/09 1:33 PM:
-------------------------------------------------------------
Hi! What's the rationale for not merging this patch (or something else solving this problem) for 2.x?
Regards //Johan (suffering from this)
was (Author: walles):
Hi! What's the rationale for not merging this patch (or something else solving this problem) for 2.x?
Regards //Johan
> 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
[jira] Commented: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Bob Fields (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130903#action_130903 ]
Carlos Sanchez commented on MNG-3518:
-------------------------------------
I think Maven should keep the old behavior for snapshot timestamps created by maven but should change for the rest to behave as OSGi does
> 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
[jira] Updated: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3518:
------------------------------
Fix Version/s: 2.1
> 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
> Fix For: 2.1
>
> 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
[jira] Updated: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "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
[jira] Commented: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Johan Walles (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204594#action_204594 ]
Johan Walles commented on MNG-3518:
-----------------------------------
Hi! What's the rationale for not merging this patch (or something else solving this problem) for 2.x?
Regards //Johan
> 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
[jira] Closed: (MNG-3518) Handle date qualifier in
DefaultArtifactVersion
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3518.
----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.x / Backlog)
Assignee: Benjamin Bentmann
> 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
> Assignee: Benjamin Bentmann
> 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