Panic this afternoon (Madrid, Spain: GMT 1) after updating from the dashboard.

Tomorrow will try to fix the problems. Let's see this "project configurators" (as I 've read recently, maven doesn't suck, but our pom does)

Thanks for the POST.

Greetings.

This is just way too disruptive. All of our existing POMs exhibit numerous errors, with apparently no configurators available on the update sites. We will have to revert to STS 2.7 until everything "just works" after upgrading to STS 2.8.
This is a real shame, the Java 7 support was much anticipated…

After upgrading to 2.8 and uninstalling the m2e 0.10, I restarted my STS. I went to the extensions tab, but I don't see any m2eclipse patch.

Where in the world did it go? How am I supposed to put it back now?

Tomorrow will try to fix the problems. Let's see this "project configurators" (as I 've read recently, maven doesn't suck, but our pom does)

@Andrew, I keep getting a 404 whenever I try both links. Anyway, I've Googled and found http://m2eclipse.sonatype.org/sites/m2e and installed 0.12 on top of STS 2.8.

Everything works as before except whenever I restart my STS I'm advised to upgrade my existing Maven projects after I upgrade to m2e 1.0 which doesn't exist in the extensions tab nor on the links you've provided.

Extended report after importing 3 Spring Roo projects:

> Right click -> Import… -> Existing projects into workspace

· Select root directory
· Copy projects into workspace (just in case..)

> A warning for the project, that won't compile until it's upgrade to M2E v1.0 appears. Click YES to upgrade now (instead of doing later by going to: Project -> Configure -> Convert legacy Maven Projects…)

> The aplicationContexts don't compile: Right click on the project -> Maven -> Update project configuration…

It successfully builds the project and open the Roo shell (take care of having previous Roo version if you project need so)

roo> perform tests
[INFO] Scanning for projects…
…
[INFO] ——————————————
[INFO] BUILD SUCCESS
[INFO] ——————————————
[INFO] Total time: 2:12.241s
[INFO] Finished at: Wed Oct 19 10:59:47 CEST 2011
[INFO] Final Memory: 8M/75M
[INFO] ——————————————

Hi,

After following your upgrade instructions, all my pom.xml files have the "Plugin execution not covered by lifecycle configuration" error. I tried getting m2e project configurators but it didn't find any extensions. I seem to be stuck. Any suggestions?

Thanks,

– Gary

Any chance that STS will be taking care of providing a patch for this m2e issue related to the "Plugin execution not covered by lifecycle configuration" error?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
This is currently a showstopper for me for upgrading to 2.8, as I can't change existing pom files just to make m2e happy.

I'm on Eclipse 3.7.1, Maven Integration for Eclipse 0.12.1, and STS 2.7.2. I don't have the other four Maven plugins specified above.

I assume that I first have to uninstall Maven Integration for Eclipse 0.12.1. When I did this, it failed with the following:

An error occurred while uninstalling
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.maven.ide.eclipse.editor 0.12.1.20110112-1712 –> null, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
Error while loading manipulator.
Error while loading manipulator.

The detail from the .log file:

!ENTRY org.eclipse.equinox.p2.engine 4 4 2011-10-19 08:41:11.312
!MESSAGE An error occurred while uninstalling
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2011-10-19 08:41:11.312
!MESSAGE session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.maven.ide.eclipse.editor 0.12.1.20110112-1712 –> null, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2011-10-19 08:41:11.312
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:63)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:107)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.java:32)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:149)
at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:78)
at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174)
at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I'm in the same boat, where m2e does not show on the extensions page; note that for some reason, I didn't have all 5 prior maven packages to remove — so I removed the ones I did have.

Currently going to http://download.eclipse.org/technology/m2e/releases to get the m2e directly (just wish I could do so from the extensions tab).

I tried to update my STS unfortunately I encountered problems when searching for m2e on Dashboard Extension. I do it on different way, go to (Help – Install New Software – then add the update site of m2e which is now on eclipse.org "http://download.eclipse.org/technology/m2e/releases") then select the "Maven Integration for Eclipse" – next next accept finish. Restart your STS.

After restarting the STS, I switch my workspace to my old workspace and you will see that the "M" indicator for Maven is missing then a pop-up display that says "convert your legacy maven blah blah…" of course yes. After converting it you will see now the "M" on your Project icon which means it was successfully converted. Just to make sure if your project was converted, restart your STS and then you will not see the pop-up message again.

Use the http://download.eclipse.org/technology/m2e/releases and install it using the old way. Help – Install New Software – Add. Then add the update site then select Maven Integration for Eclipse then install it.

After installing it you will see the "M" indicator is missing which means for "Maven". Or if you're not on your old workspace, just switch to that workspace and then a pop-up message that says convert legacy maven… Just convert it and then after converting, the "M" indicator will appear on your project icon.

@Andrew, I'm reverting back to 0.12 m2e. My Maven projects are not building. m2e is suggesting me to search for m2e connectors. It found one for the buildhelper but it didn't solve whatever problem it's trying to fix.

Unfortunately, the affected areas are plugins and their lifecycles. It has nothing to do with my code. And another unfortunate thing is my projects won't compile. The tests won't run. That's when I decided this update is bad.

Also, take a look at this blog detailing a similar bad experience: http://grumpyapache.blogspot.com/2011/08/mess-that-is-m2e-connectors.html

@Andrew Eisenberg: it happens when the pom contains any maven plugin which is not available in the m2e lifecycle mappings directory (I can count less than 20 from Preferences->Maven->Discovery->Open Catalog – Lifecycles checkbox), in my case it was maven-antrun-plugin running the hibernate bytecode instrumentation – I agree that also your patch would be very useful and I added myself in CC as I don't see any way to vote on m2e's bugzilla

I did a fresh install instead of an upgrade. We have dozens of maven projects making up our system that use the cxf-codegen-plugin which generates code from wsdl and places it under /target. This worked well with m2eclipse (selecting all projects and clicking Maven->Update Project Configuration would do the trick). This does not work with m2e – the code is generated but never added to the Eclipse project build paths. I have 132 broken projects now.

There is no m2e project configurator for the cxf-codegen-plugin.

Thanks Andrew, I will give it a try again when I have some more time and let you know. Had to go back to previous release to get some work done today..

How do I know which version of eclipse is my STS working with?

I had long time without running my STS. So today I ran it and performed a 'BIG' updating of STS plus all the plugins and stuff.

Now, STS is on the 2.8.0 version but going to About/ then click the eclipse.org icon, the version says: (I supposed the current version for indigo was 3.7.1)

-Eclipse Platform
Version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi
Build id: M20110210-1200

-Eclipse Java Development Tools
Version: 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
Build id: M20110210-1200

Do I need to update my eclipse? How do I do that?

Thanx

Hi,

Is there another way to get stuff from the catalog? I have a bunch of osgi related plugins.

The catalog appears to be empty when I hit it from Maven->Discovery – I get a warning that it is empty and to check my network connection (which is fine).

Building is working from the command line though – so I'm not blocked.

Regards,
Jon

I just reverted back to the old m2e version but my STS is upgraded to 2.8 STS.

After reverting back, whenever I right-click on any project and select Maven my menus are displayed twice. Luckily my projects are under SVN. So using revert, it changed back my Eclipse settings for each project.

Everything works fine but from time to time that ugly m2e side-effects are showing, i.e I get a null error in my pom.xml. I don't know the exact error because it only shows null whenever I point my mouse on it. To fix it, I just delete it in the Markers window.

Hi,

I've tried everything, upgrading to version 2.8 and a clean install of 2.8, but I can't seem to fix errors in my pom.xml files. Unfortunately, I'm going to have to go back to 2.7 so I can get some work done. Does anyone know where I can find the STS 2.7 download? I can't find it on the download page.

Thanks,

– Gary J.

P.S. I still love Spring and the STS IDE. One bad upgrade experience won't change that fact.

For those looking for older "stable" versions, you can visit http://www.springsource.com/downloads/sts.

Previous versions that really worked for me are:

springsource-tool-suite-2.7.2.RELEASE-e3.7
springsource-tool-suite-2.6.1.SR1-e3.6.2

If you're going to try 2.8, I suggest downloading and installing it FRESH. Then "TRY" out your existing Maven projects with it. Don't mess with your existing STS installation which I DID. It was a bad decision. My existing projects are behaving erratically after the upgrade.

The projects worked with a FRESH installation of 2.8 with the caveat that you have to IGNORE some of your Maven plugins. If you're upgrading from 2.6 or 2.7, even selecting the IGNORE will behave erratically. So do yourself a favor. Install FRESH!

Hi there…

I cant find any connector for org.codehaus.mojo:buildnumber-maven-plugin:1.0 so I still get the "Plugin execution not covered by lifecycle configuration" error, any ideas?

Please help.

I did a fresh install of STS 2.8 for windows 7 using the exe installer in the root directory.

I did File > Import > Existing projects into workspace

I was asked to upgrade legacy maven project. I clicked 'Yes'

I had errors on POM so I did – Maven > Update project coonfiguration

I then got this error: "Unable to update maven configuration for the following projects. Problems encountered while setting project description."

The POM error I got is: "org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, org.apache.maven.archiver.MavenArchiveConfiguration)"

What is causing this? What should I do?

@Andrew

Below is the error log after updating the legacy maven project and doing.. Maven > Update project configuration:

eclipse.buildId=2.8.0.201110171000-RELEASE
java.version=1.6.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.springsource.sts.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.springsource.sts.ide

Warning
Sat Oct 22 10:21:52 PDT 2011
Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:2.3.1: Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1

Warning
Sat Oct 22 10:21:52 PDT 2011
The POM for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1 is missing, no dependency information available

Warning
Sat Oct 22 10:21:52 PDT 2011
Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.4.1: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1

Warning
Sat Oct 22 10:21:52 PDT 2011
The POM for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 is missing, no dependency information available

I also don't see a reference to the maven archiver plugin on my pom.xml and Effective POM. The maven plugins reference I have in my pom.xml are:

maven-compiler-plugin
maven-war-plugin

STS is also showing errors on a jquery file (jquery-1.6.2.min.js). This file is in a 'resources' folder under the 'webapp' folder.

I didn't have issues in sts 2.7.2. What else can I do?

@Andrew

The log errors I posted on my previous post was from a separate, fresh install of a new STS 2.8.0 and also used a new, fresh workspace. This is the environment where I imported my maven project into, using the option to 'copy' the maven project into the new workspace.

I tried your recommendation about removing the workspaceState.ser file but I didn't find one. Maybe because it is STS 2.8 with m2e 1.0.

Now I still have my 'other' old install of STS 2.7.2 which I upgraded to 2.8 but still have the legacy m2eclipse ver. 0.12.1 on it. My project builds fine on this one. STS just prompts me to upgrade the legacy maven project which I just decline.

I tried to revert it back to STS 2.7.2 using Help > About > Installation details > Revert… but I just get this error:

"An error occurred while collecting items to be installed
session context was:(profile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: org.eclipse.update.feature,com.springsource.sts.package,2.7.2.201109131000-RELEASE"

Since I am not able to revert back, I intend to just continue using this upgraded STS 2.8 with the m2eclipse ver. 0.12.1 until the issues with the new m2e 1.0 get sorted out.

Are there other means for me to revert this back to STS 2.7.2?
Will it break my project later on if I continue using the upgraded STS 2.8 with this older m2eclipse?

I have error with below link
http://dist.springsource.com/release/TOOLS/third-party/m2e/

Oh man, I only read down to the installation section. So when I noticed some maven files had errors I was just about to ask but there you go again reading my mind! Thanks for the post.

This update caused a number of problems among our project team. One is that it seems that "upgraded" projects are not backward-compatible, so once a project is upgraded, everyone has to get the new STS. But there are two much bigger problems. The first is that aspects defined in one project do not seem to be woven in dependent projects. This worked in 2.7. We are building with ajdt, as far as I can see. The second is that inter-project dependencies seem to flake out when projects are first loaded, which has been quite painful for many of our developers. We found a workaround – building the top (the independent module) of the dependency tree outside STS, using maven on the command-line.

I second that! My engineering team will not be moving to the new release until a working upgrade option is available, or at least direct support for the older m2e 0.12 (i.e. choosing that version cleanly upon install, without having to uninstall/reinstall/revert back, etc..)

Sonatype should be ashamed of themselves for not giving their customers a smooth transition path, but this is not the first time they've done this and it probably won't be the last. We are now looking into maven alternatives to avoid repeating these types of catastrophes.

These are terrific news.

I'm using STS 2.8.0 but I'm not affected by the issues that have been explained all along the answers of this blog.

In spite of this, I must to compliment you on your job: you're going to fulfill all the client requests in a very short time. You're excellent programmers and developers. Congratulations!

Well done.

I had been having some trouble with this issue, in my STS 2.8 installation – I'd uninstalled what I could uninstall of the Maven integration that I could find, in the process of, trying to update to the m2eclipse plugins. I didn't know that I should uninstall the Tycho item, however. So, that's a great help, there – thanks a bunch!

Thank you, thank you, thank you!
I spent half a day trying to figure out
what got hosed on my setup. A coworker pointed me
to your article and it fixed the maven issue.

For better search engine hits, here are some of my
details.

An internal error occurred during: "Updating Maven Dependencies".
org/eclipse/m2e/core/internal/embedder/ExtensionModule

java.lang.NoClassDefFoundError: org/eclipse/m2e/core/internal/embedder/ExtensionModule

Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.m2e.core (1312).

m2e – Maven Integration for Eclipse 1.0.200.20111228-1245 org.eclipse.m2e.feature.feature.group Eclipse.org – m2e