[ 
https://issues.apache.org/jira/browse/IVY-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlo de Wolf updated IVY-1036:
-------------------------------

    Description: 
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}

  was:
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:
{{<ivysettings>
   <settings defaultResolver="snapshots.jboss.org"/>
   <resolvers>
      <ibiblio name="snapshots.jboss.org" m2compatible="true" usepoms="true" 
root="http://snapshots.jboss.org/maven2"/>
   </resolvers>
</ivysettings>}}

Ivy won't go through the unique snapshot versions:
{{      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}}

With the maven-snapshot-resolver it will:
{{<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>}}

{{      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)}}


> latest.integration isn't resolved against a maven snapshot repository
> ---------------------------------------------------------------------
>
>                 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
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to