[
http://jira.codehaus.org/browse/MNG-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134770#action_134770
]
manuel aldana commented on MNG-2456:
i got same problem. for the start i workarounded this by
[
http://jira.codehaus.org/browse/MNG-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126536
]
Brian Fox commented on MNG-2456:
Can someone produce an IT for this?
Maven Archiver creates incorrect Class-Path entry in
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_84865 ]
Christian Goetze commented on MNG-2456:
---
I would like to see a fix that does not involve adding extra configuration
items to the assembly... whatever happened to
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_74484 ]
Max Bowsher commented on MNG-2456:
--
I think the true issue is in the core component maven-artifact-manager, in the
DefaultArtifactResolver class - which, in the case of a
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_74198 ]
Max Bowsher commented on MNG-2456:
--
I think this issue should be reopened. It is true that an outputFileNameMapping
can provide a workaround, but that's only a workaround,
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_71722 ]
Baerrach bonDierne commented on MNG-2456:
-
Oops. Classpath is missing file extension...
Need to update tests and repatch.
Maven Archiver creates incorrect
