Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Plugin execution not covered by lifecycle configuration 
Not exactly. Let me explain...

There was never a really meaningful default. What we had did not work
well or did not work at all for many projects. Probably even worse, it
not always worked for many projects, so we had to go through series of
refresh/update dependencies/update configuration/rebuild voodoo (or "m2e
dance" as some called it) to get projects in a good state. For example
MNGECLIPSE-823 [1] was the most voted issues in m2e jira and it was a
direct manifestation of this "flakiness".

The solution we came up with, when fully implemented (!), is expected to
work well for all supported projects out-of-the-box, i.e. without any
changes to pom.xml, but fail fast and gracefully for unsupported
projects, in which case the users will be able to use explicit pom.xml
configuration as a workaround. When you import one of supported projects
in m2e workspace, m2e automatically discovers and installs any
additional required software, so the project "just works" without any
changes to pom.xml.

For this to work, however, m2e needs a library of lifecycle mapping
metadata and corresponding project configurators and we hope m2e user
and adopter community will help growing and maintaining this library.
And if you are interested to help, you can start by submitting an
enhancement request m2e bugzilla. If you want to implement support for
"not covered" plugins used by your project, please join m2e-dev mailing
list and we'll be happy to provide pointers.

Of course, there is a chance we overlooked another, simpler solution, so
if you think you know how to make m2e work reliably and efficiently with
all/many projects while failing gracefully for the rest, please bring
this up on m2e-dev and I will see how is the best to schedule this.


[1] https://issues.sonatype.org/browse/MNGECLIPSE-823

--
Regards,
Igor

On 11-05-26 04:54 PM, Jochen Wiedmann wrote:

Thanks, Igor, for the explanation. Let me summarize, what I read from that:

Because of some "long-standing issues" and some "rogue maven plugins"
you choosed to invent a system that enforces registration of every
Maven plugin in the so-called lifecycle configuration.

Rather than assuming a meaningful default (most possibly the same that
has been in use in the past), which ensures upwards compatibility and
reduces side effects to those users that actually notice the
"long-standing issues" and or the "rogue maven pllugins" and are thus
willing to apply some explicit configuratiom, you make us all change
tons of poms that have been working perfectly well in both native
Maven and m2eclipse?

Is that it?



On Thu, May 26, 2011 at 9:35 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>  wrote:

I started to write some documentation explaining what's going on and
what to do about it at [1].

[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered

--
Regards,
Igor

On 11-05-26 02:49 PM, Ben Tatham wrote:


Can someone please explain to me why we have to add all
the pluginExecutionFilters for all of the specific plugins eveywhere to
work around this problem?  Why did it work in Helios without this, but
in newer Indigo versions, we have to muddle our pom's with
eclipse-specific stuff?

Thank,
Ben

On Thu, Apr 7, 2011 at 6:52 PM, Nord, James<JNord@xxxxxxx
<mailto:JNord@xxxxxxx>>  wrote:

    Ahh,

    Found out what the quickfix was actually doing under the hood – so
    configured the lifecycle plugin in the top level parent pom

    /James

    *From:*m2e-users-bounces@xxxxxxxxxxx
    <mailto:m2e-users-bounces@xxxxxxxxxxx>
    [mailto:m2e-users-bounces@xxxxxxxxxxx
    <mailto:m2e-users-bounces@xxxxxxxxxxx>] *On Behalf Of *Nord, James
    *Sent:* 07 April 2011 22:36
    *To:* m2e-users@xxxxxxxxxxx<mailto:m2e-users@xxxxxxxxxxx>
    *Subject:* [m2e-users] Plugin execution not covered by lifecycle
    configuration

    Hi,

    I’m trying the M6a Indigo and M build of M2e.

    I’m hitting a major problem in that our build has many issues with
    plugins that have no lifecycle config in m2e.

    Whilst I understand the reason for the error I am happy to ignore
    this I can only do it for one plugin per module at once – which
    means there is a tedious job of ignoring 150+ lifecycle issues.

    Is there a way to ignore multiple lifecycle issues at once? (eclipse
    used to allow you to find related issues and fix them all with the
    same quick fix IIRC)

    Regards,

                     /James


  ------------------------------------------------------------------------



  **************************************************************************************
    This message is confidential and intended only for the addressee. If
    you have received this message in error, please immediately notify
    the postmaster@xxxxxxx<mailto:postmaster@xxxxxxx>  and delete it
    from your system as well as any copies. The content of e-mails as
    well as traffic data may be monitored by NDS for employment and
    security purposes. To protect the environment please do not print
    this e-mail unless necessary.

    NDS Limited. Registered Office: One London Road, Staines, Middlesex,
    TW18 4EX, United Kingdom. A company registered in England and Wales.
    Registered no. 3080780. VAT no. GB 603 8808 40-00

  **************************************************************************************


    _______________________________________________
    m2e-users mailing list
    m2e-users@xxxxxxxxxxx<mailto:m2e-users@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/m2e-users




--
Ben Tatham
Software Developer
Nanometrics Inc.
+1 613-592-6776 x254
http://www.nanometrics.ca

Back to the top