Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] How to tell m2e to update a particular folder (or at least: "target" folder) after <pluginExecution>?

The first problem is to decide when m2e should execute the mojo. Doing
so every time a workspace file changes is both prohibitively expansive
from performance point of view and results in endless builds. There are
few ways of doing this but all require either development of a project
configurator to "wrap" mojo execution or changes to the mojo itself.

So yes, just adding <refresh> annotation either won't do what you want,
i.e. automatic generation and refresh, or will result in extremely poor
workspace build performance and endless build loops.

--
Regards,
Igor


On 12-07-10 12:50 PM, Markus Karg wrote:
Well, I have neither experience nor time for Eclipse Plugins development, so I won't bother the developers with things that might be impossible from the Eclipse side.

What I would expect from the user's view (and this is why I stay on THIS mailing list to express the pure user's view) simply would be this:

<execute>
	<refresh>target/generated-sources/java/xslt</refresh>
</execute>

Would this break something? Effectively it would offload the responsibility of when-to-refresh and what-to-refresh explicitly to the POM author.

Regards
Markus

-----Urspr√ľngliche Nachricht-----
Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Igor Fedorenko
Gesendet: Dienstag, 10. Juli 2012 10:47
An: m2e-users@xxxxxxxxxxx
Betreff: Re: [m2e-users] How to tell m2e to update a particular folder (or at least: "target" folder) after <pluginExecution>?

This question comes up every now and then but so far nobody was able to suggest a good general solution that solves the problem for all/most projects without breaking anything. This does not mean such solution is not possible, of course, so if you think you know how to implement it, please bring your ideas to m2e-dev mailing list, preferably in a form of a quality patch with corresponding tests, and we'll discuss it there.

--
Regards,
Igor

On 12-07-10 11:02 AM, l.penet@xxxxxxxx wrote:
On 09/07/2012 21:45, Igor Fedorenko wrote:
You need a project configurator. <execute/> mapping is the last
resort thing and is not expected to work for any mojo that generates
workspace resources.

http://wiki.eclipse.org/M2E_plugin_execution_not_covered
I understand our concern but isn't it a lot of work (and to know) for
"simple users" of m2e ?

It is always easy to ask others to avoid you some work, but...
I have the same need and it seems to me (but I must be missing
something) that an element in m2e configuration indicating a
dynamically generated dir would solve most cases.

By the way, thank you for your work.

Ludovic
|
| AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
|

_______________________________________________
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
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users




Back to the top