Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Specifying Project Builders/Nature

m2e does not directly add/remove natures or builders. This is done acco
project project configurators, which are determined based on project
build lifecycle mapping.

For example, maven-compiler-plugin with compilerId=javac is mapped to
m2e-jdt project configurator, which will enable java nature and builder
for projects that use maven-compiler-plugin.

Wiki [1] explains where m2e looks for lifecycle mapping configuration
and you can see effective lifecycle mapping in Eclipse project
properties. The wiki also explains how lifecycle mapping can be
configured in project pom.xml, so you can override undesired mapping at
project level.

[1] https://wiki.eclipse.org/M2E_plugin_execution_not_covered

--
Regards,
Igor

On 2014-10-10, 13:25, CoderPlus Team wrote:
Consider a Maven Project which is imported into Eclipse.If I'm correct,
m2eclipse reads the pom file adds the required natures and build
commands to the project.All of this is done automatically.


With m2e, it was possible to specify the project nature as configuration
to the maven-eclipse-plugin.


How can this be done? For example, I don't want the JavaScript Nature to
be automatically added to a maven project(which has a few js files). Is
this possible?

Similarly is it possible to force a nature on a project?


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users



Back to the top