[
http://jira.codehaus.org/browse/MEAR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191310#action_191310
]
Maarten Billemont commented on MEAR-66:
---------------------------------------
This *IS* a bug. If only because of its inconsistent behavior. Building an
EAR artifact with dependencies that are in the reactor and have a finalName
specified results in a *different* resulting EAR artifact than building the EAR
artifact without the dependencies in the reactor.
This is not only a problem with the manifest, but, for instance, JBoss uses the
archive name to build the JNDI mapping of EJBs. If the name of the archive is
unpredictable (because you don't know how it will be built; either with or
without the dependencies in the reactor), the JNDI mapping that JBoss will use
when deploying the archive is unpredictable and your EJBs are inaccessible half
the time.
When copying the dependencies, their finalName should be considered and their
destination name should conform to it.
> finalName taken into account for full build but not for ear build
> -----------------------------------------------------------------
>
> Key: MEAR-66
> URL: http://jira.codehaus.org/browse/MEAR-66
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Windows XP; JDK1.5
> Reporter: Mark Jeffery
> Assignee: Stephane Nicoll
> Attachments: build.zip, j2ee-1.0.jar
>
>
> If I force a build of all projects via a parent pom (which build 2 EARS),
> then the finalName attribute of the jar plugin is taken into account for the
> dependencies when they are built.
> If I quickly build one EAR only, via its pom, it retrieves the dependencies
> from the repository, the finalName in the dependency pom is not taken into
> account and the version number is added to the jar name.
> This breaks the manifest entries for the jars that were built with the forced
> build as they still reference the specified name but the jars included in the
> EAR have the version on the name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
