[
http://jira.codehaus.org/browse/MEAR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97170
]
Stephane Nicoll commented on MEAR-66:
-------------------------------------
it has nothing to do with the EAR plugin. It's a manifest thing. The ear plugin
does not read the manifest, it just applies the rules that are given by the
configuration.
finalName is only applicable for the current project, not for dependencies
manipulated by a project.
> 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
