4 Replies Latest reply on Mar 20, 2012 7:30 AM by maxandersen

Upgrade from JBoss Tools 3.3.0 M5 to Beta 1 broke my Maven war modules in Eclipse

sslavic Mar 16, 2012 5:44 AM

Hello JBoss Tools community,

After upgrading to JBoss Tools 3.3.0.v20120302-0221-H55-Beta1 for war modules following error marker started appearing on maven-war-plugin default execution declaration:

"Multiple annotations found at this line:

- Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-war-plugin:2.1.1:war (execution: default-war, phase: package)

- Project configurator "org.jboss.tools.maven.seam.configurator" is not available. To enable full functionality, install the project configurator and run Maven->Update

Project Configuration."

Updating project configuration doesn't help.

Wanted to revert back to M5 but that failed at first. I upgraded JBoss Tools together with JRebel plugin, and JRebel doesn't seem to leave old versions on their repo, neither does JBoss Tools on development repo, breaking eclipse configuration revert feature.

Luckly I had a recent copy of eclipse installation archive/bundle so I'm back at M5 again.

Apart from reverting to M5, does anyone have any other suggestions/workarounds/explanations on what's wrong with Beta1 and can I do something to fix it?

Kind regards,

Stevo.

1. Re: Upgrade from JBoss Tools 3.3.0 M5 to Beta 1 broke my Maven war modules in Eclipse

david.salter Mar 16, 2012 12:55 PM (in response to sslavic)

I've not experienced any problems updating to Beta1 with my Maven projects, but I don't have JRebel installed. Can you post the bit of your pom that has the errors on it?
Actions
2. Re: Upgrade from JBoss Tools 3.3.0 M5 to Beta 1 broke my Maven war modules in Eclipse

maxandersen Mar 19, 2012 10:23 AM (in response to sslavic)

did you try the quickfix which will install the features for you ?

and if not, did by any chance *not* install the jboss tools maven plugins for i.e. maven.seam.configurator ?

Anything shows up in your error log when launching eclipse ?
Actions
3. Re: Upgrade from JBoss Tools 3.3.0 M5 to Beta 1 broke my Maven war modules in Eclipse

sslavic Mar 19, 2012 12:46 PM (in response to maxandersen)

There was nothing special with maven-war-plugin execution, it was just declared, no special configuration, just plain default execution.

I'm not sure, but as far as I can remember there were no quickfixes available, nothing special/related was in logs, and plugin was installed. Will try again.

Btw, here is link to this broken eclipse bundle/installation: http://dl.dropbox.com/u/11530426/eclipse-3.7-SR2-Full--broken.zip (~600MB)
Actions
4. Re: Upgrade from JBoss Tools 3.3.0 M5 to Beta 1 broke my Maven war modules in Eclipse

maxandersen Mar 20, 2012 7:30 AM (in response to sslavic)

The problem markers you refer to about "execution context not covered" should have a quick fix available offering to search/download the proper integration plugin.

I know it sucks but does the same problem occur if you simply just install Beta1 directly without doing an update ?

Upgrading from milestones to beta1 should work, but we did do some feature reorgs for Beta which might make such update fail.
Actions

Go to original post