Re: [m2e-users] wst nature added to project after upgrading m2e and ecli

[John Prestel <jprestel@xxxxxxxxxxxxxxxxxxxxx>]

Fred,

Thanks very much for the information, and for the comment on the ticket (https://bugs.eclipse.org/bugs/show_bug.cgi?id=409856)!

For the time being, I've done a hacky workaround of removing the feature dir and plug-in jars from the eclipse installation. I haven't seen any negative effects yet, but I presume this isn't the best approach. I assume, too, that the files will be restored on the next Kepler upgrade.

On Tue, Jun 4, 2013 at 10:02 AM, Fred Bricon <fbricon@xxxxxxxxx> wrote:

m2e-wtp can't be disabled for the moment at the workspace level. Please open a feature request at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP

As a workaround, you can tell m2e to ignore the m2e-wtp configurator(s) directly in your pom. 

You need to add the following snippet to your pom.xml  :

<profiles>

<profile>

<id>m2e</id>

<!-- This profile is only activated when building in Eclipse with m2e -->

<activation>

<property>

<name>m2e.version</name>

</property>

</activation>

<build>

<pluginManagement>

<plugins>

<plugin>

<groupId>org.eclipse.m2e</groupId>

<artifactId>lifecycle-mapping</artifactId>

<version>1.0.0</version>

<configuration>

<lifecycleMappingMetadata>

<pluginExecutions>

<pluginExecution>

<pluginExecutionFilter>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-war-plugin</artifactId>

<versionRange>[2.0.1,)</versionRange>

<goals>

<goal>war</goal>

</goals>

</pluginExecutionFilter>

<action>

<ignore />

</action>

</pluginExecution>

</pluginExecutions>

</lifecycleMappingMetadata>

</configuration>

</plugin>

</plugins>

</pluginManagement>

</build>

</profile>

</profiles>

See http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse.m2e.wtp/lifecycle-mapping-metadata.xml for the other plugin executions that may need to be overriden in your pom.xml (replace <configurator> block with <ignore/>)