[ http://jira.codehaus.org/browse/MASSEMBLY-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131055#action_131055 ]
Dirk Olmes commented on MASSEMBLY-311: -------------------------------------- If you're talking about regular dependencies I agree with you that specifying an empty filename mapping could behave like this. However, in the very special case of a system scoped dependency I would have expected that the filename is left alone, resulting in a plain copy of the dependency as is. How do I achieve this? > Empty outputFileNameMapping creates zip entries with no name > ------------------------------------------------------------ > > Key: MASSEMBLY-311 > URL: http://jira.codehaus.org/browse/MASSEMBLY-311 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug > Affects Versions: 2.2-beta-2 > Environment: Maven 2.0.9 > Reporter: Dirk Olmes > Priority: Trivial > Attachments: assembly-with-system-dependency.zip > > > I'm working on a project that has system dependencies. I want to package > those dependencies with their original name into the assembly (i.e. use the > same name of the JAR as in the system path). > Leaving the outputFileNameMapping in the assembly descriptor's dependencySet > creates ZipEntries in the resulting zip file but those don't have a name. > Example: > {code} > unzip -qql target/assembly.zip > 0 04-16-08 16:20 assembly/ > 2205737 04-07-08 18:23 assembly/lib/ > 2621 04-16-08 16:20 assembly/lib/ > {code} > Note the second line ... > I have attached a sample project that uses Maven's uber Jar as system scope > dependency. Run the test with mvn -DMAVEN_HOME=.... package assembly:assembly > to create the zip. -- 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