- manifest generation has been tested in multi module configuration and generally works (you can test some archetype from
http://code.google.com/p/open-archetypes/ ).
- it depends on the mavenarchiver plugin from m2e-extras, which hasn't changed between m2e-wtp 0.14.0 and m2e-wtp 0.15.0
- MECLIPSEWTP-226 has strictly no relation with your issue, this was a problem of having a bad manifest in one of the m2e-wtp plugins itself.
And now the questions :
- what project(s) display the error? the utility one(s) or the war?
- is your manifest generated via a custom plugin?
- can you provide a more complete stacktrace of the issue? See under <workspace>/.metadata/.log?
- can you show me your pom.xml (you can remove / obfuscate any sensible data)?
I think the problem is with nested module. I have a multi-module
project. 2 Projects are the utils-projekt and have be included in
web-project. The utils-projekts generate the MANIFEST.MF and this is
a problem. If i remove MANIFEST.MF from target, the error is
resolved.
I have update from the WTP 0.14 to WTP 0.15.1 and become the Error
in Eclipse: - Error:
org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest)
We have a plugin for creating of the MANIFEST.MF. The MANIFEST.MF
we create in target and if our plugin create the file. The Eclipse
show in pom.xml this error. I know that the WTP 0.15.1 has any
changes for MANIFEST.MF(https://issues.sonatype.org/browse/MECLIPSEWTP-226
).
I have this problem with m2 1.0 and m2 1.1. And get this error
only is I install WTP 0.15.1