Resolution: Won't Fix
Affects Version/s: 2.2, 2.2.1, 2.3
Fix Version/s: None
I have the following project layout (which is part of a big project, this pattern is used many times)
A-ear -> A-ejb -> A-jar -> B-jar
All these projects are built in the same reactor.
A-ejb used automatic CLASSPATH generation in its pom-file.
B-jar uses the FinalName directive to specify a final name to be used.
In A-ear B-jar is correctly packaged with its final name.
But in A-ejb the MANIFEST.MF file contains not the final name for B-jar, but the standard one (i.e. as if no FinalName would have been selected).
This problem exists since version 2.2 of the plugin. Up to now we used 2.1, which works perfectly. I assume the new archiver (version 2.4) that has been introduced in 2.2 causes the problem.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1309d 10h 20m||1||Michael Osipov||25/Nov/14 14:49|
|Workflow||jira [ 12957655 ]||Default workflow, editable Closed status [ 12994989 ]|
|Project Import||Sun Apr 05 23:33:58 UTC 2015 [ 1428276838376 ]|
|Workflow||jira [ 12720188 ]||Default workflow, editable Closed status [ 12751075 ]|
|Project Import||Sun Apr 05 09:46:33 UTC 2015 [ 1428227193041 ]|
|Field||Original Value||New Value|
|Resolution||Won't Fix [ 2 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|