Return-Path: 
 <notifications-return-7591-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 4246 invoked from network); 4 Mar 2009 08:30:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Mar 2009 08:30:27 -0000
Received: (qmail 87988 invoked by uid 500); 4 Mar 2009 08:30:27 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 87962 invoked by uid 500); 4 Mar 2009 08:30:27 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 87953 invoked by uid 99); 4 Mar 2009 08:30:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 00:30:27 -0800
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 08:30:17 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 20D72234C4AC
	for <notifications@ant.apache.org>; Wed,  4 Mar 2009 00:29:56 -0800 (PST)
Message-ID: <1891532401.1236155396120.JavaMail.jira@brutus>
Date: Wed, 4 Mar 2009 00:29:56 -0800 (PST)
From: "Carlo de Wolf (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVY-1036) latest.integration isn't resolved
 against a maven snapshot repository
In-Reply-To: <529688067.1235722752933.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ 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.