[
https://issues.apache.org/jira/browse/MEJB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966101#comment-17966101
]
Olivier Lamy commented on MEJB-18:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ejb-plugin#73|https://github.com/apache/maven-ejb-plugin/issues/73].
> Manifest classpath contains wrong entries in multi-module build
> ---------------------------------------------------------------
>
> Key: MEJB-18
> URL: https://issues.apache.org/jira/browse/MEJB-18
> Project: Maven EJB Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Joerg Schaible
> Priority: Blocker
> Attachments: MEJB-18.zip
>
>
> We had to detect, that in multi-module builds the entries in the Manifest for
> the classpath for those artifacts can be wrong that are also part of the
> build. The incident occurs, if an artifact is build in a SNAPSHOT version,
> but the EJB refers this artifact in a released version. The manifest contains
> nevertheless an entry for the SNAPSHOT.
> Additional observations:
> * the target/effective-pom.xml contains the dependency with the right version
> * the manifest contains the correct entry classpath when the artifact is
> build locally
> This is a real blocker, since building the EAR. Maven will copy the *correct*
> released version of the artifact, but the EJB is broken, because of the wrong
> (and missing) dependency.
> It seems the component creating the manifest uses a wrong dependency
> resolution for multi module builds ... might be the maven-archiver ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
