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>?

I have no knowledge of the intera of Eclipse or m2e, but I do not see why it shall be so hard to explain to the m2e plugin source code that a newly invented <refreshGuiFolderViewOnJustThisFolderAfterBuildIsCompletelyDone> pom tag (with the folder name as child) shall simply update the UI, while I as a human should be able to do exactly this? The only reason I can think of is that the Eclipse IDE does not trigger such an event (which I do not assume).

-----Urspr√ľngliche Nachricht-----
Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von l.penet@xxxxxxxx
Gesendet: Donnerstag, 12. Juli 2012 14:35
An: m2e-users@xxxxxxxxxxx
Betreff: Re: [m2e-users] How to tell m2e to update a particular folder (or at least: "target" folder) after <pluginExecution>?

On 12/07/2012 08:48, Markus Karg wrote:
> Why do you think that the complete workspace will be refreshed? I explicitly suggested (and am practicing) to refresh one single folder (what DOES NOT imply any harmful side effects for days no, working on multiple machines in different Eclipse releases). Why should refreshing one single target folder trigger a refresh of the entire workspace? Your horror scenario will happen only if unchanged folders will get refreshed (what I did not propose) or either Eclipse or the plugin executions touch unchanged files (what in my case does not happen, as the XML plugin does not do anything unless the source is changed).
> I understand your theory, but it simply does not happen -- at least on our PCs in the past days.
As far as I (intuitively) understands it, there is quite a difference between inserting a refresh step in a build process and manually requesting a refresh after the build is done.

The build process, in eclipse or maven, is complex. Refreshing an output file can trigger other actions. For instance, if your dynamic folder contains java source (as it is my case), it might trigger a build.

When you process that yourself, you know that it is ok for your case. 
And that you can safely just "refresh".

You refresh only *once* and *after* the build is finished. You will not constantly refresh, after each build, but just when you need it. That can be something difficult to explain to a computer.

Best regards,


m2e-users mailing list

Back to the top