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