| Hi Jason,
Thanks for your answer.
It's a good argument. However, the same effect could be obtained if the configuration was in another file (e.g. org.eclipse.m2e.core.prefs).
I'm asking because there is a lot of criticism about the pom.xml complexity. Adding configuration that is not related to the build can make it even worse. :(
Cheers,
Henrique On 23/06/2011, at 21:15, Jason van Zyl wrote: On Jun 23, 2011, at 7:53 PM, Henrique Prange wrote: Hi all,
I'm playing with Eclipse Indigo and m2e for the first time. Thanks for your hard work and congratulations.
The first thing I have noted about m2e is that most of my projects contain errors related to plug-in goal execution. m2e provides an automatic mechanism to add the required configuration to ignore the goal execution, which is fine. The configuration is written to the pom.xml and has the following comment:
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
If this is a m2e specific configuration and has no influence on the Maven build, why is it in the pom.xml? Is it a temporary solution?
These changes are stored in the pom.xml so that if you check in those changes and someone else on your team imports the project, they will not be subject to the errors you encountered.
Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl---------------------------------------------------------
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
|
