You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Schley Andrew Kutz (JIRA)" <ji...@codehaus.org> on 2011/02/04 17:48:22 UTC

[jira] Created: (MNG-5002) Artifact metadata file names are corrupted with the text "local"

Artifact metadata file names are corrupted with the text "local"
----------------------------------------------------------------

                 Key: MNG-5002
                 URL: http://jira.codehaus.org/browse/MNG-5002
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 3.0.2
         Environment: Windows XP SP 3
            Reporter: Schley Andrew Kutz
            Priority: Critical
         Attachments: NvnArtifactMetadata.java

I have a custom MOJO where in I add a piece of metadata to the project's primary artifact. I've extended the AbstractArtifactMetadata class to do so. The getLocalFilename and getRemoteFilename methods simply return a string in the following format $artifactId-$version.nvn. In Maven 2.2.1 the file would get stored in the repository properly. For example, emc-vsi-core-features-4.1.0-SNAPSHOT.nvn is how the file should look, and does in Maven 2.2.1. In Maven 3 the file resembles emc-vsi-core-features-4-local.1.0-SNAPSHOT.nvn. Clearly the new local resolution logic in Maven 3 is inserting the text "local" into the metadata's file name prior to storing it on the file system.

I'm simply invoking the primary artifact's addMetadata method and passing it an instance of my custom class. I've attached my metadata class to this bug report.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira