Filtered MANIFEST not added to generated EAR
--------------------------------------------
Key: MEAR-103
URL: http://jira.codehaus.org/browse/MEAR-103
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Reporter: Luca Masini
When resource filtering is enabled filtered resources are written into the
${project.build.directory}/${project.build.finalName} directory.
In our test case we have to filter the MANIFEST.MF file, from the
src/main/application/META-INF directory.
But the EAR generator (JarArchiver) reads the MANIFEST in its default original
location ${basedir}/src/main/application/META-INF/MANIFEST.MF, and there is not
filtered.
The workaround is to change the manifestFile attribute so that it reads
directly the generated file, but I think this is a plugin misbehaviour, it
should automatically manage such a situation where the MANIFEST.MF is filtered.
--
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
