Bug 353751

Description Kees van Dieren 2011-08-03 08:34:05 EDT

Build Identifier: 20110615-0604

When updating from m2e 0.10 or m2e 0.12 to m2e 1.0, everything seems to work fine: import projects from old workspace, compile projects. Eclipse doesn't show any errors / porlbmes, and junit tests work fine.

However, workspace resolution does not work.

Further investigation showed up that m2e configuration is not updated, and that the new m2e doesn't work with the old m2e configuration. Well, in fact it all looks ok, no errors / warnings are shown.

Current situation:
Everything looks fine, but workspace resolution doesn't work.

Desired situation:
Fail explicit with error / problem, such as: project configuration is for older M2E version which is incompatible with current
OR 
automatically run 'update project configuration' for all projects that have m2e configuration settings of an older version, after eclipse project import or eclipse startup

Reproducible: Always

Steps to Reproduce:
1.create a workspace with Eclipse 3.5 multi module project, with 2 modules, and maven goals that need workspace resolution.
2. Verify that workspace resolution goes fine in eclipse 3.5
3. Open this workspace in Eclipse 3.7
4. Run maven goal with workspace resolution enabled.
5. No workspace resolution happens.