[
https://jira.codehaus.org/browse/MWAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328920#comment-328920
]
Jens Bannmann commented on MWAR-300:
------------------------------------
Never mind, this *does* work correctly after all. I managed to forget the @
character after the groupId placeholder. The following mapping works:
{noformat}@{groupId}@_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
Please close this issue as 'invalid' or the like.
> 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:
> {noformat}@{groupId}_@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@{noformat}
> The files in WEB-INF/lib, however, do not have their group ID in the file
> name. For example, a GSON jar file I depend on is copied as
> {noformat}@{groupId}_gson-2.2.2.jar{noformat}
> instead of the expected name
> {noformat}com.google.code.gson_gson-2.2.2.jar{noformat}
> 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
