ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVY-1396) Ivy generating wrong revision in URL for sample Maven artifact
Date Mon, 17 Dec 2012 22:26:12 GMT

    [ https://issues.apache.org/jira/browse/IVY-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534378#comment-13534378
] 

Maarten Coene commented on IVY-1396:
------------------------------------

Could you try 2.3.0-RC1 to see if you have the same problem?
We changed something to the SNAPSHOT resolving in 2.3.0-RC2 and it would be very helpfull
to find out if it was already broking in 2.3.0-RC1 or not.
                
> 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
>            Priority: Minor
>         Attachments: build.xml, ivysettings.xml, ivy.xml, pom.xml
>
>
> 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

Mime
View raw message