Re: [m2e-users] Plugin execution not coveredby lifecycleconfiguration

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=335711

This was originally scheduled for 1.0 but we ran out of time and had to
postpone it for a later release.

We are also open for fundamentally different ideas about how to
implement Maven and Eclipse workspace, so bring them up on m2e-dev
mailing list.

--
Regards,
Igor

On 11-06-27 6:53 PM, Christian Schneider wrote:
> I think it is fair that the community starts to provide some plugins.
> But the next step should be to analyze the commonalities and perhaps
> we (community + m2e team) can offer some more generic solutions that
> each cover a larger set of maven plugins. For example
> I think code generation is quite similar you have some sources to read
> from, generate some other sources that you then want to have in the
> source folders of eclipse.
>
> Christian
>
>
> Am 27.06.2011 16:44, schrieb Igor Fedorenko:
> > We could not find a general solution that would properly and reliably
> > work for all Maven projects. The old "default" behaviour available in
> > 0.12 did not work for large enough number of projects to make it
> > prohibitively expansive for our team to support. I strongly believe
> > opensource is about community working together to solve common problems.
> > Our primary goal right now is to help m2e community build library of m2e
> > extensions that provide lifecycle mapping for various maven plugins. I
> > don't think it is fair to expect m2e dev team to provide
> > out-of-the-box support for all maven plugins.
> >
> > --
> > Regards,
> > Igor