You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Matt Benson (JIRA)" <ji...@apache.org> on 2012/10/16 21:37:03 UTC
[jira] [Resolved] (IVY-1036) latest.integration isn't resolved
against a Maven snapshot repository (when uniqueVersion = true)
[ https://issues.apache.org/jira/browse/IVY-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson resolved IVY-1036.
------------------------------
Resolution: Fixed
Fix Version/s: trunk
No response; patch seems to be working properly.
{code}
Committed revision 1398943.
{code}
Should be in Ivy v2.4.0 but that version hasn't yet been added to JIRA.
> latest.integration isn't resolved against a Maven snapshot repository (when uniqueVersion = true)
> -------------------------------------------------------------------------------------------------
>
> Key: IVY-1036
> URL: https://issues.apache.org/jira/browse/IVY-1036
> Project: Ivy
> Issue Type: New Feature
> Affects Versions: 2.0
> Reporter: Carlo de Wolf
> Assignee: Matt Benson
> Labels: patch
> Fix For: trunk
>
> Attachments: IVY-1036.patch.txt, MavenSnapshotResolver.java
>
>
> When latest.integration is the requested revision the ibiblio resolver doesn't go through the snapshots. So in effect you'll always end up with the latest.release.
> Given the following ivysettings:
> {code:title=ivysettings.xml}
> <ivysettings>
> <settings defaultResolver="snapshots.jboss.org"/>
> <resolvers>
> <ibiblio name="snapshots.jboss.org" m2compatible="true" usepoms="true" root="http://snapshots.jboss.org/maven2"/>
> </resolvers>
> </ivysettings>
> {code}
> Ivy won't go through the unique snapshot versions:
> {noformat}
> listing revisions from maven-metadata: http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/maven-metadata.xml
> found revs: [0.13.1-SNAPSHOT, 1.0.1-SNAPSHOT]
> HTTP response status: 404 url=http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/0.13.1-SNAPSHOT/jboss-ejb3-cache-0.13.1-SNAPSHOT.pom
> CLIENT ERROR: Not Found url=http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/0.13.1-SNAPSHOT/jboss-ejb3-cache-0.13.1-SNAPSHOT.pom
> HTTP response status: 404 url=http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/1.0.1-SNAPSHOT/jboss-ejb3-cache-1.0.1-SNAPSHOT.pom
> CLIENT ERROR: Not Found url=http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/1.0.1-SNAPSHOT/jboss-ejb3-cache-1.0.1-SNAPSHOT.pom
> {noformat}
> With the maven-snapshot-resolver it will:
> {code:title=ivysettings.xml}
> <ivysettings>
> <typedef name="maven-snapshot-resolver" classname="org.jboss.ejb3.ivy.plugins.resolver.MavenSnapshotResolver"/>
> <settings defaultResolver="snapshots.jboss.org"/>
> <resolvers>
> <maven-snapshot-resolver name="snapshots.jboss.org" m2compatible="true" usepoms="true" root="http://snapshots.jboss.org/maven2"/>
> </resolvers>
> </ivysettings>
> {code}
> {noformat}
> listing revisions from maven-metadata: http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache/maven-metadata.xml
> found revs: [0.13.1-SNAPSHOT, 1.0.1-SNAPSHOT]
> snapshots.jboss.org: found md file for org.jboss.ejb3#jboss-ejb3-cache;latest.integration
> => http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-cache//1.0.1-SNAPSHOT/jboss-ejb3-cache-1.0.1-20090303.040911-22.pom (1.0.1-20090303.040911-22)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira