Re: [m2e-users] What features does m2e provide by examining plugin confi

["KARR, DAVID" <dk068x@xxxxxxx>]

> -----Original Message-----
> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-
> bounces@xxxxxxxxxxx] On Behalf Of Anders Hammar
> Sent: Friday, August 31, 2012 8:07 AM
> To: Maven Integration for Eclipse users mailing list
> Subject: Re: [m2e-users] What features does m2e provide by examining
> plugin configurations?
> 
> Not sure what you're looking for. How would tooling support that
> interrogates some configuration give any benefit on it's own?

One of my arguments is that a declarative build system (Maven) vs. an imperative or procedural build system (Ant) allows for tooling that can implicitly "understand" the build, and can better provide automated assistance for the build.  It seems obvious that since plugin configurations are well-defined, m2e should be able to (and likely does) check for the presence of configuration for specific plugins and modify its behavior to fit.

I'm just looking for examples of that in m2e.

> The things I argue that m2e will give you (if you have fairly well
> modeled projects and also follow best-practice and use well
> know/working plugins) are:
> * "incremental" (or maybe rather runtime) build support (extremely
> nice when you use code generation - change the model, save and you
> have the generated output without having to manually build) - However,
> please understand that m2e and Maven doesn't fix this on it's own! You
> have to use good Maven plugins and, most importantly, there has to be
> integration for m2e (a connector or in the plugin). Having Ant
> scripting in the POM will not give you this!
> * Good help in viewing your dependencies and track down
> strange/incorrect ones

These are good points, and are in line with what I'm looking for.

> There might be more, depending on preferences.
> 
> These things would also be true comparing using Maven to Graddle or
> any other build tool without any support in the IDE. It might be ok
> from command-line, but I argue you shouldn't be there - you should be
> working in the IDE!
> 
> /Anders
> 
> On Fri, Aug 31, 2012 at 4:06 PM, KARR, DAVID <dk068x@xxxxxxx> wrote:
> > I'm preparing a couple of presentations arguing a transition from Ant
> to Maven for an organization.  I'm gathering background information
> about Maven-related tools.
> >
> > I noticed in a recent note here that m2e provides some features by
> interrogating the configuration of specific plugins in the project pom.
> Could some of you give me a list of several significant features in m2e
> that are provided by interrogating plugin configurations?
> > _______________________________________________
> > m2e-users mailing list
> > m2e-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/m2e-users
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users