[
https://issues.apache.org/jira/browse/IVY-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534862#comment-13534862
]
Nick Spacek edited comment on IVY-1396 at 12/18/12 12:53 PM:
-------------------------------------------------------------
I tested it under RC1 and definitely saw different behavior; it is unable to
resolve any version of the artifact from the remote Maven repository. I've
attached output logs for RC1 and RC2 (hopefully there's no private information
in them!).
was (Author: nickspacek):
Output logs under RC1 and RC2
> 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, 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
