I think the only long term solution is to populate m2e marketplace
catalog with lifecycle mapping configuration for various maven plugins.
Everything else is a stop-gap solution that does not really solve much.
--
Regards,
Igor
On 11-06-27 1:52 PM, [email protected] wrote:
Hum...well that would be a downside, but I'm not convinced that placing
all this eclipse-specific stuff in the POM is the way to go. I'd prefer
to have common configuration in the preferences, and the ability to
override on a project-specific basis, like a lot of the other project
settings. If that isn't possible, I'd still prefer to replicate the
config in each project's settings than pollute my poms with IDE noise.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Igor Fedorenko
Sent: 27 June 2011 10:47
To: [email protected]
Subject: Re: [m2e-users] Plugin execution not covered by
lifecycleconfiguration
Lifecycle mapping configuration stored outside of pom.xml will not be
inherited from parent to child modules. For typical multimodule project
this means the same config has to be replicated for every module.
--
Regards,
Igor
On 11-06-27 1:45 PM, [email protected] wrote:
Just a quick q...why can this not be stored in the eclipse project
settings rather than in the POM? It seems to me that it doesn't really
belong in the POM.
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
