maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Bley (JIRA)" <>
Subject [jira] (MNG-5459) failure to resolve pom artifact from snapshotVersion in maven-metadata.xml
Date Fri, 05 Apr 2013 06:22:52 GMT
Claudio Bley created MNG-5459:

             Summary: failure to resolve pom artifact from snapshotVersion in maven-metadata.xml
                 Key: MNG-5459
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 3.0.5, 3.1.x
            Reporter: Claudio Bley
         Attachments: mvn-snapshot-resolve-fix.diff

We're using Artifactory on the server side, and ivy / sbt to publish artifacts  upstream.

After publishing several -SNAPSHOT versions of a project, trying to use it from Maven, resulted
in a warning and ultimately a build failure because it cannot determine the dependencies:

{code}[WARNING] The POM for is missing, no dependency
information available{code}

This is the corresponding maven-metadata-snapshots.xml:

As you can see, the <value> for the jar artifact and the pom artifact differ:


Apparently, artifactory optimizes the case when an artifact doesn't change; it does not create
a new file, but just links to the existing one.

Maven, however, takes a shortcut and makes the erroneous assumption that the values for pom
and jar artifact always match up.

The attached patch fixes this.

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:

View raw message