Re: [m2e-users] WTP 0.15.1 and M2 1.0 or 1.1 Error: org.codehaus.plexus.

[Fred Bricon <fbricon@xxxxxxxxx>]

I messed up the project when creating the issue. It is 
https://github.com/sonatype/m2eclipse-extras/issues/10

Fred Bricon

/me needs more sleep

On Mon, Feb 20, 2012 at 1:26 PM, work@xxxxxxxxxxx <work@xxxxxxxxxxx> wrote:

Thank you very much for you help.

Am 20.02.12 11:39, schrieb Fred Bricon:

Ok so the problem comes from the use of maven-jar-plugin 2.4. The mavenarchiver plugin uses reflection to invoke Manifest operations. 

maven-jar-plugin 2.4 uses plexus-archiver 2.1 which has removed the "merge" public methods on the org.codehaus.plexus.archiver.jar.Manifest. This prevents the mavenarchiver to work properly.

Your immediate workaround is to fallback on maven-jar-plugin 2.3.2.

I opened  https://github.com/sonatype/m2eclipse-wtp/issues/5 to keep track of this issue.

Regards,

Fred Bricon

On Mon, Feb 20, 2012 at 10:15 AM, work@xxxxxxxxxxx <work@xxxxxxxxxxx> wrote:

Hi,
Am 17.02.12 20:21, schrieb Fred Bricon:

First a few observations :

- 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?

the error display in the utility projekts

- is your manifest generated via a custom plugin?

yes, we generated with custom plugin

- can you provide a more complete stacktrace of the issue? See under <workspace>/.metadata/.log?

I see nothing in log, which say, you have any problem with m2.

- can you show me your pom.xml (you can remove / obfuscate any sensible data)?

I have a simple project, this project has in target MANIFIEST.MF. This manifest was created with our plugin. The project hasn't a sensible data. If you import the project in Eclipse, than you must see the error in views Problems. I have it for me. Cation don't run clean from maven. In this case you delete MANIFEST.MF

Regards

Regards,

Fred Bricon

On Fri, Feb 17, 2012 at 4:20 PM, work@xxxxxxxxxxx <work@xxxxxxxxxxx> wrote:

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.

Alexander.
Am 17.02.12 15:46, schrieb work@xxxxxxxxxxx:

Hi,

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

How i can get WTP 0.14

Alexander

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

--
"Have you tried turning it off and on again" - The IT Crowd

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

--
"Have you tried turning it off and on again" - The IT Crowd

--
"Have you tried turning it off and on again" - The IT Crowd