Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Thu, 20 Dec 2012 23:19:13 +0000 (UTC)
From: "Maarten Coene (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <JIRA.12624265.1355747881168.39243.1356045553260@arcas>
In-Reply-To: <JIRA.12624265.1355747881168@arcas>
References: <JIRA.12624265.1355747881168@arcas>
Subject: [jira] [Resolved] (IVY-1396) Ivy generating wrong revision in URL
 for sample Maven artifact
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Maarten Coene resolved IVY-1396.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0
         Assignee: Maarten Coene

Fixed in both trunk and 2.3.x-branch.
Thanks for reporting this issue!
                
> Ivy generating wrong revision in URL for sample Maven artifact
> --------------------------------------------------------------
>
>                 Key: IVY-1396
>                 URL: https://issues.apache.org/jira/browse/IVY-1396
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0-RC2
>            Reporter: Nick Spacek
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: build.xml, ivysettings.xml, ivy.xml, pom.xml, rc1.log, rc2.log
>
>
> I'm having some troubles with Ivy resolving the wrong latest.integration for a Maven artifact. It is reading the Maven metadata (apparently)and determining that there is a 0.0.3-SNAPSHOT version. Strangely, it then attempts to retrieve a POM that is using both the 0.0.3-SNAPSHOT version from the metadata and a 0.0.1-SNAPSHOT version that it could have only discovered using the metadata for that particular version, as you will see below. As far as I can tell, the Maven metadata is fine.
> I've put together a sample. A simple, empty Maven artifact, and an Ivy build that resolves it.
> I deployed three version of Maven artifact at 0.0.1-SNAPSHOT. Each time I asked Ivy to resolve, it was successful. When I updated the version to 0.0.2-SNAPSHOT, it began mixing the URLs.

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