Fundamentally, m2e-specific configuration is no different from, for example, maven-site-plugin configuration or any other maven plugin configuration, and one could argue that pom.xml is _the_ place for all project configuration, including m2e-specifics.
In more practical term, pom.xml provides configuration inheritance and property expansion mechanisms, which I believe greatly simplify configuration of the most common case -- when the same m2e lifecycle mapping applies to all modules of a multi-module project. -- Regards, Igor On 11-08-14 6:50 PM, Philippe Bastiani wrote:
Thanks Igor for this link... Yes, I agree with the idea of ??m2e-specific configuration outside of the POM. You said that there are certain advantages of storing this information in pom.xml file ! The referenced issue shows no benefit... So, what are these advantages ? Regards,
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
