Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] change in default behaviour of <execute/> mapping

Thanks for the reply. I actually thought about it. I even wanted to make my next connectors smarter by checking whether the source files have changes and invoke plugin only if they do. That should not cause the endless loop, but should allow automatically generating sources without the need of full build or updating maven configuration.


On Fri, Nov 30, 2012 at 3:56 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
Take code generation mojo, like maven-modello-plugin. When invoked
during eclipse incremental build, it unconditionally generates output
.java files. This triggers JDT builder to produce .class files. This
triggers new invocation of modello plugin, which unconditionally
generates .java files, which triggers JDT builder produce .class files
and so on.

There are also less obvious scenarios when JDT builder escalates
incremental build to full without telling the other builders about this.

I did talk about this during eclipsecon eu 2012, and there is more info
on the subject, including (lousy) ppt animations of the events.

http://www.eclipsecon.org/europe2012/sessions/m2e-exercise-mixing-oil-and-water


--
Regards,
Igor


On 12-11-30 2:32 AM, Aliaksei Lahachou wrote:
Hello Igor,

could you explain or give an example of situation causing an endless
loop? I think I've seen this behavior a couple of times, but I would
like to know better what's causing it.

Regards,
htfv (Aliaksei Lahachou)

Am 30.11.2012 04:10 schrieb "Igor Fedorenko" <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>>:


    As of m2e 1.2, <execute/> mapping has runOnIncremental=true by default.
    This causes endless builds when <execute/> is used for a mojo that is
    not compatible with m2e incremental workspace build. I am changing the
    default to runOnIncremental=false in 1.3. Projects and maven plugins
    that support incremental build will need to explicitly state so to work
    in 1.3, otherwise they will be only invoked during full/clean build.

    https://bugs.eclipse.org/bugs/__show_bug.cgi?id=395433

    <https://bugs.eclipse.org/bugs/show_bug.cgi?id=395433>

    --
    Regards,
    Igor
    _________________________________________________
    m2e-dev mailing list
    m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/__mailman/listinfo/m2e-dev
    <https://dev.eclipse.org/mailman/listinfo/m2e-dev>




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

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


Back to the top