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.