You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jens Bannmann (JIRA)" <ji...@codehaus.org> on 2013/07/18 14:17:05 UTC

[jira] (MWAR-300) Group ID not usable in outputFileNameMapping

Jens Bannmann created MWAR-300:
----------------------------------

             Summary: Group ID not usable in outputFileNameMapping
                 Key: MWAR-300
                 URL: https://jira.codehaus.org/browse/MWAR-300
             Project: Maven 2.x WAR Plugin
          Issue Type: Bug
    Affects Versions: 2.3
            Reporter: Jens Bannmann


I configured the following output file name mapping:

    @{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@

The files in WEB-INF/lib, however, do not have their group ID in the file name, so a GSON jar file is named literally

    @{groupId}_gson-2.2.2.jar

instead of the expected name

    com.google.code.gson_gson-2.2.2.jar

It seems the group ID is simply not supported by outputFileNameMapping.

Note: The page <http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mapping.html> only says "You can use any property of Artifact and ArtifactHandler as a token.", but does not offer a list of valid tokens - even a link to the relevant Maven source files would have been fine.

--
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