Igor Fedorenko wrote:
I've seen in the console the m2eclipse using the eclipse:m2eclipse
mojo, which uses the same config information.
So, what is the relationship between your plugin and the maven
plugin: maven-eclipse-plugin:m2eclipse?
I think Eugene already explained on another thread that m2eclipse can
be configured to execute arbitrary maven plugins during project
import/configuration.
That is not what I said and also to eliminate any confusion m2eclipse
currently does not expose any configuration for executing goals to the
user. However there is a project configurator that runs
maven-eclipse-plugin before other configurators, so custom natures and
other things from the m-e-p configuration in pom.xml should go into
Eclipse project configuration. Some of that configuration could be
overwitten by configurators that runs after it. Though because m-e-p
plugin does it outside of Eclipse there is some chance that Eclipse
won't see those changes.
And although I do not completely understand the reasons, by default
m2eclipse executes m-e-p:eclipse and m-e-p:m2eclipse goals if m-e-p
configuration is present in the pom. These goals have lowest priority
among project configuration steps, and most/all of the metadata they
create will be overwritten.
Lowest priority mean that m-e-p configurator is executed before others
and as you know other configurators are not supposed to overwrite things
such as natures or facets they don't responsible to.
The reasons m-e-p is being invoked are quite simple. pom.xml could
have additional configuration for Eclipse project that need to be picked up.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
