-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.6.2.RELEASE
-
Fix Version/s: 3.7.0.RELEASE
-
Component/s: maven.plugin
-
Labels:None
Someone else summed up the stack trace here:
Now I looked at:
and I see "org.apache.maven.project;resolution:=optional" ...
I guess it is optional due to the dynamic / replacable Maven runtimes, however all Spring code that uses it should check it is currently in a resolved with the OSGi container, before using code path that rely on it to exist.
I also do not see in the MANIFEST.MF
Require-Bundle: org.eclipse.m2e.maven.runtime
As if I look at eclipse-jee-luna-SR1-win32-x86_64/plugins/org.eclipse.m2e.maven.runtime_1.6.0.20141015-1550/META-INF/MANIFEST.MF I see it is provided here and this m2e plugin comes with all m2e installs to provided the mandatory embeded implementation.