[
https://issues.apache.org/jira/browse/MEJB-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966090#comment-17966090
]
Olivier Lamy commented on MEJB-51:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ejb-plugin#93|https://github.com/apache/maven-ejb-plugin/issues/93].
> Classpath is wrong for projects using "FinalName" directive
> -----------------------------------------------------------
>
> Key: MEJB-51
> URL: https://issues.apache.org/jira/browse/MEJB-51
> Project: Maven EJB Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2, 2.2.1, 2.3
> Reporter: Thomas Arand
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
