Is there a chance you installed m2e-wtp as part of the upgrade? It is
part of Kepler release common repository and is not hard to install by
accident. It is also included in "for Java EE" eclipse package.
--
Regards,
Igor
On 2013-06-03 6:39 PM, John Prestel wrote:
Running Eclipse Kepler (Java EE), I updated my m2e installation to
1.4.0.20130525-03100 (from 1.4.0.20130521-1115). At that time, I also
received an upgrade for Eclipse itself, going to version
2.0.0.20130528-1545 (from 2.0.0.20130509-1008).
When I opened up my workspace, m2e complained that my existing projects
were no longer up-to-date, and indicated that I should update them from
the pom. When I did so, I got several changes to my settings, project,
and classpath files. These led to new errors reported in the Problems
tab, so I tried reverting the changes. However, after reverting, Eclipse
immediately modified my project file again, adding in a wst nature:
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
as well as a new build command:
<buildCommand>
<name>org.eclipse.wst.common.project.facet.core.builder</name>
<arguments>
</arguments>
</buildCommand>
I'm not sure if m2e is responsible for this addition, or if this is
coming from changes in the Java IDE. Can you possibly shed any light?
Thanks so much!
John
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
