[
http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=188451#action_188451
]
François LEIBER commented on MJAR-28:
-
Any progress on this? I'm still having the issue with latest
[
http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165937#action_165937
]
Dale Wyttenbach commented on MJAR-28:
-
Currently the Fix Version for this issue is None. In what
[
http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105944
]
Todd Nine commented on MJAR-28:
---
I'm also experiencing this. We're working on a huge project with about 15 sub
projects. This
[
http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105948
]
Max Bowsher commented on MJAR-28:
-
Todd: The local workaround that I'm using consists of:
1) Check out maven-archiver-2.2
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_78430 ]
Martin Desruisseaux commented on MJAR-28:
-
Maybe related to this issue: the manifest classpath generated by Maven ignores
the real JAR name as specified in
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74197 ]
Max Bowsher commented on MJAR-28:
-
Perhaps this issue should be closed, then, if the problem is located entirely
within maven-archiver, and the patch attached here does not
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74095 ]
Max Bowsher commented on MJAR-28:
-
Baerrach: Do you mean MJAR-28-patch.txt ? If so, I don't see how it can do
that, since it seems mostly to be a tree reorganization and
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74100 ]
Baerrach bonDierne commented on MJAR-28:
Sorry you are right.
The changes I needed to make for this are in maven-archiver in the linked issue
MNG-2456 as the archiver
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74020 ]
Max Bowsher commented on MJAR-28:
-
I do not agree that this issue should be closed.
It is true that outputFileNameMapping provides a workaround, but it is only a
workaround,
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74025 ]
Baerrach bonDierne commented on MJAR-28:
The patch I provided does just that, for SNAPSHOTS it uses the timestamped
version instead of -SNAPSHOT.
Using the jar
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_72186 ]
Baerrach bonDierne commented on MJAR-28:
In MASSEMBLY-67 John Casey says
The solution here is to use an outputFileNameMapping such as this:
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_70120 ]
Baerrach bonDierne commented on MJAR-28:
Most of the comments I have made have been against MASSEMBLY-67 but the bug I
believe is definitely in Maven Archiver (no bug
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_69271 ]
Baerrach bonDierne commented on MJAR-28:
Woops, I've attached the comments to bug MASSEMBLY-67.
Never mind, they are related.
Request for advice sent to dev list, see
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_68535 ]
Brett Porter commented on MJAR-28:
--
yep, the manifest should contain the actual file name (ie, timestamped)
Using the jar plugin with addClasspath and snapshots can create manifest
14 matches
Mail list logo