ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Benson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IVY-1036) latest.integration isn't resolved against a maven snapshot repository
Date Mon, 15 Oct 2012 20:53:03 GMT

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

Matt Benson edited comment on IVY-1036 at 10/15/12 8:51 PM:
------------------------------------------------------------

I have a failing test for this, cloned from {{ResolveTest#testResolveMaven2Snapshot1()}} :
{code}
    public void testResolveMaven2Snapshot1AsLatestIntegration() throws Exception {
        // test case for IVY-1036
        // here we test maven SNAPSHOT versions handling, 
        // with m2 snapshotRepository/uniqueVersion set to true
        // but retrieving by latest.integration
        Ivy ivy = new Ivy();
        ivy.configure(new File("test/repositories/m2/ivysettings.xml"));
        ResolveReport report = ivy.resolve(
            ModuleRevisionId.newInstance("org.apache", "test-SNAPSHOT1", "latest.integration"),
            getResolveOptions(new String[] {"*(public)"}), true);
        assertNotNull(report);
        assertFalse(report.hasError());

        // dependencies
        assertTrue(getIvyFileInCache(
            ModuleRevisionId.newInstance("org.apache", "test-SNAPSHOT1", "2.0.2-SNAPSHOT")).exists());
        assertTrue(getArchiveFileInCache(ivy, "org.apache", "test-SNAPSHOT1", "2.0.2-SNAPSHOT",
            "test-SNAPSHOT1", "jar", "jar").exists());
    }
{code}

What I am lacking is any idea how to go about addressing the issue.  :(
                
      was (Author: mbenson):
    I have a failing test for this, cloned from {{ResolveTest#testResolveMaven2Snapshot1()}}
:
{code}
    public void testResolveMaven2Snapshot1AsLatestIntegration() throws Exception {
        // test case for IVY-1036
        // here we test maven SNAPSHOT versions handling, 
        // with m2 snapshotRepository/uniqueVersion set to true
        // but retrieving by latest.integration
        Ivy ivy = new Ivy();
        ivy.configure(new File("test/repositories/m2/ivysettings.xml"));
        ResolveReport report = ivy.resolve(
            ModuleRevisionId.newInstance("org.apache", "test-SNAPSHOT1", "latest.integration"),
            getResolveOptions(new String[] {"*"}), true);
        assertNotNull(report);
        assertFalse(report.hasError());

        // dependencies
        assertTrue(getIvyFileInCache(
            ModuleRevisionId.newInstance("org.apache", "test-SNAPSHOT1", "2.0.2-SNAPSHOT")).exists());
        assertTrue(getArchiveFileInCache(ivy, "org.apache", "test-SNAPSHOT1", "2.0.2-SNAPSHOT",
            "test-SNAPSHOT1", "jar", "jar").exists());
    }
{code}

What I am lacking is any idea how to go about addressing the issue.  :(
                  
> 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
>              Labels: patch
>         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.
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