Well, I'm not sure I fully understand your point. like for anyother plugin explicitely executed through the <execute/> tag, it is the developper responsibility to guarantee (through the use of the build-helper for instance) that the generated / updated sources are correctly handled by the Eclipse build. The only difference would be that the maven plugin would only be executed for certain maven execution id(s) and ignored for others. Of course the other configuration options remain, i.e. incremental build participation, version filter, ... However, I must admit that I'm not aware of the M2E internals and it might definitely be more complicated than one can think at first.
Best, Vincent 2012/10/19 Igor Fedorenko <[email protected]> > I can see why it may be desired to run general purpose plugins during > Eclipse build, but I don't see an easy way to implement that. Even if we > limit support to full workspace build only, m2e will still need to know > all files inside workspace created/update/deleted during plugin goal > execution, which likely means hard to maintain and error prone manual > configuration in each mapping. > > -- > Regards, > Igor > > > On 12-10-19 3:49 AM, Vincent Vandenschrick wrote: > >> Hi Igor, >> >> Thank you for your detailed answer. Regarding the use-case, it may not >> be relevant for plugins that are dedicated to very specific tasks but it >> may be important for more general-purpose plugins. One real-life example >> I have on one of our projects is the use of the exec plugin whose java >> goal is triggered multiple times. One of this execution is needed for >> code generation (later included by the build-helper) whereas the others >> can be safely ignored to speed-up the eclipse build. antrun would be >> another example of such general-purpose plugin that would benefit from >> an execution id filtering. >> >> Of course, I can hear the voice saying "just make a maven plugin out of >> this legacy code"... But I still believe it would be a quick win for >> M2E. May I still open an RFE ? >> >> Thanks, >> Vincent >> >> >> ______________________________**_________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> >> >> ______________________________**_________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
