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

This is not a theory, this was observed in practice for other similar cases... but feel free to prove me wrong.
-- 
Sent from my SGS

Markus Karg <karg@xxxxxxxxx> 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.
>
>-----Ursprüngliche Nachricht-----
>Von: m2e-users-bounces@xxxxxxxxxxx
>[mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Igor Fedorenko
>Gesendet: Mittwoch, 11. Juli 2012 16:24
>An: m2e-users@xxxxxxxxxxx
>Betreff: Re: [m2e-users] How to tell m2e to update a particular folder
>(or at least: "target" folder) after <pluginExecution>?
>
>No, most likely it will not work for you either. The only reason you do
>not see endless build loop is because you press F5 only once. The
>following sequence will happen if workspace is refreshed automatically
>
>User presses Ctrl-S
>Workspace broadcasts resource change event(s) This triggers workspace
>build Maven build runs, (re)generates sources and refreshes workspace
>Workspace broadcasts resource change event(s) This triggers workspace
>build JDT builder runs and (re)generates .class files Workspace
>broadcasts resource change event(s) This triggers workspace build Maven
>build runs, (re)generates sources and refreshes workspace ... and so on
>forever
>
>I actually plan to propose an advanced talk about more interesting
>problems integrating Maven into Eclipse Workspace for this coming
>eclipsecon eu. Can't promise the talk will be accepted, of course.
>
>
>--
>Regards,
>Igor
>
>On 12-07-11 5:08 PM, Markus Karg wrote:
>> Igor,
>>
>> still you do not understand me: I sayd MY WORKSTATION does not run in
>any troubles if I do the refresh on the named folder, so I suggest an
>OPTIONAL feature for explicit refresh on an explitly named folrder,
>which I will enabled in my POM. So nothing will happen to anybody: For
>me it will work (and possibly for others) and for everybody not
>explicitly enabling it nothing will change.
>>
>> Regards
>> Markus
>>
>> -----Ursprüngliche Nachricht-----
>> Von: m2e-users-bounces@xxxxxxxxxxx 
>> [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Igor Fedorenko
>> Gesendet: Mittwoch, 11. Juli 2012 16:05
>> An: m2e-users@xxxxxxxxxxx
>> Betreff: Re: [m2e-users] How to tell m2e to update a particular
>folder (or at least: "target" folder) after <pluginExecution>?
>>
>> And as I said earlier, blindly running maven build after each
>resource change will result in poor performance and endless build
>loops. It does not matter if this is done through m2e extension or
>implemented in m2e core itself.
>>
>> --
>> Regards,
>> Igor
>>
>> On 12-07-11 5:00 PM, Markus Karg wrote:
>>> Well, possibly easy for you, but as I said, I have no idea how 
>>> Eclipse plugin coding works... (and doubt that spending days into 
>>> learning is worth the effort as it is not a public solution then)
>>>
>>> *Von:*m2e-users-bounces@xxxxxxxxxxx
>>> [mailto:m2e-users-bounces@xxxxxxxxxxx] *Im Auftrag von *Matthew 
>>> Piggott
>>> *Gesendet:* Mittwoch, 11. Juli 2012 15:43
>>> *An:* Maven Integration for Eclipse users mailing list
>>> *Betreff:* Re: [m2e-users] How to tell m2e to update a particular 
>>> folder (or at least: "target" folder) after <pluginExecution>?
>>>
>>> Its fairly easy to write a connector to do this for you.
>>>
>>> On 11 July 2012 09:16, Markus Karg <karg@xxxxxxxxx 
>>> <mailto:karg@xxxxxxxxx>> wrote:
>>>
>>> Well, in fact Pressing CTRL-S followed by F5 neither produces
>endless 
>>> builds nor needs any measurable time on my workstation. Actually it 
>>> runs in less than a second. So I really would love to see the 
>>> possibility for
><refresh>target/generated-sources/java/xslt</refresh>
>>> or something like that in a future release, so people like me can 
>>> optionally enable this. :-)
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>
>>> [mailto:m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>] Im Auftrag von Igor
>Fedorenko
>>> Gesendet: Mittwoch, 11. Juli 2012 14:13
>>>
>>> An: Maven Integration for Eclipse users mailing list
>>>
>>> Betreff: Re: [m2e-users] How to tell m2e to update a particular 
>>> folder (or at least: "target" folder) after <pluginExecution>?
>>>
>>>
>>> Ah, ok. This is Run As Maven launch configuration. No plans to
>remove 
>>> it, so no worries there. It is not possible to execute as part of 
>>> Ctrl-S however, and you almost certainly don't want to do that for 
>>> performance reasons and endless builds I mentioned.
>>>
>>> --
>>> Regards,
>>> Igor
>>>
>>> On 12-07-11 3:08 PM, Dave Hartnoll wrote:
>>>   > OK, attached as 'refresh.jpg'.
>>>   >
>>>   > Dave.
>>>   >
>>>   > -----Original Message-----
>>>   > From: m2e-users-bounces@xxxxxxxxxxx 
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>
>>>   > [mailto:m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>] On Behalf Of Igor Fedorenko 
>
>>> >
>>> Sent: 11 July 2012 12:53  > To: m2e-users@xxxxxxxxxxx 
>>> <mailto:m2e-users@xxxxxxxxxxx>  > Subject: Re: [m2e-users] How to 
>>> tell m2e to update a particular folder (or at least: "target"
>folder) 
>>> after <pluginExecution>?
>>>   >
>>>   > Can you post a screenshot of your builder configuration dialog?
>>>   >
>>>   > --
>>>   > Regards,
>>>   > Igor
>>>   >
>>>   > On 12-07-11 2:39 PM, Dave Hartnoll wrote:
>>>   >> It's present in my Eclipse 4.2 with latest everything (incl.
>m2e 
>>> 1.1). Please don't remove it - I use it to get all the target
>folders 
>>> updated in the IDE after a full build.
>>>   >>
>>>   >> Dave.
>>>   >>
>>>   >> -----Original Message-----
>>>   >> From: m2e-users-bounces@xxxxxxxxxxx 
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>
>>>   >> [mailto:m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>] On Behalf Of Igor Fedorenko
>>>>> Sent: 11 July 2012 12:04  >> To: m2e-users@xxxxxxxxxxx
>>> <mailto:m2e-users@xxxxxxxxxxx>  >> Subject: Re: [m2e-users] How to 
>>> tell m2e to update a particular folder (or at least: "target"
>folder) 
>>> after <pluginExecution>?
>>>   >>
>>>   >> We've removed this from m2e 0.12 if I am not mistaken, but from
>>> 1.0 for sure.
>>>   >>
>>>   >> --
>>>   >> Regards,
>>>   >> Igor
>>>   >>
>>>   >> On 12-07-11 12:23 PM, Dave Hartnoll wrote:
>>>   >>> Hi Markus,
>>>   >>>
>>>   >>> I'm not sure if this will help, but if you are only concerned 
>>> with  >>> not having to press F5 after Maven has run then you could 
>>> set up a  >>> Run Configuration (Run->Run Configurations...) to 
>>> process the Maven build.
>>>   >>> The 'Maven Build' configuration type has a 'Refresh' tab where
>
>>> you  >>> can control what gets refreshed afterwards.
>>>   >>>
>>>   >>> Dave.
>>>   >>>
>>>   >>> *From:*m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>
>>>   >>> [mailto:m2e-users-bounces@xxxxxxxxxxx
>>> <mailto:m2e-users-bounces@xxxxxxxxxxx>] *On Behalf Of *Markus Karg
>>>>>> *Sent:* 09 July 2012 15:13  >>> *To:* m2e-users@xxxxxxxxxxx
>>> <mailto:m2e-users@xxxxxxxxxxx>  >>> *Subject:* [m2e-users] How to 
>>> tell m2e to update a particular folder  >>> (or at least: "target" 
>>> folder) after <pluginExecution>?
>>>   >>>
>>>   >>> Hello m2e Community!
>>>   >>>
>>>   >>> My pom.xml enables execution of the xml-maven-plugin (and 
>>> enables
>>>>>> generated-sources as a target folder using the
>build-helper-plugin):
>>>   >>>
>>>   >>> <configuration>
>>>   >>>
>>>   >>> <lifecycleMappingMetadata>
>>>   >>>
>>>   >>> <pluginExecutions>
>>>   >>>
>>>   >>> <pluginExecution>
>>>   >>>
>>>   >>> <pluginExecutionFilter>
>>>   >>>
>>>   >>> <groupId>org.codehaus.mojo</groupId>
>>>   >>>
>>>   >>> <artifactId>xml-maven-plugin</artifactId>
>>>   >>>
>>>   >>> <versionRange>[1.0,)</versionRange>
>>>   >>>
>>>   >>> <goals>
>>>   >>>
>>>   >>> <goal>transform</goal>
>>>   >>>
>>>   >>> </goals>
>>>   >>>
>>>   >>> </pluginExecutionFilter>
>>>   >>>
>>>   >>> <action>
>>>   >>>
>>>   >>> <execute/>
>>>   >>>
>>>   >>> </action>
>>>   >>>
>>>   >>> </pluginExecution>
>>>   >>>
>>>   >>> </pluginExecutions>
>>>   >>>
>>>   >>> </lifecycleMappingMetadata>
>>>   >>>
>>>   >>> </configuration>
>>>   >>>
>>>   >>> After pressing F5 I can see the generated outcome in Eclipse
>Indigo.
>>>   >>> Nice! J
>>>   >>>
>>>   >>> But I don't want to press F5! So how to tell m2e that after 
>>> <execute  >>> /> of the plugin, it also shall <refresh /> the 
>>> generated-sources  >>> folder in the IDE?
>>>   >>>
>>>   >>> Thanks!
>>>   >>>
>>>   >>> Markus
>>>   >>>
>>>   >>>
>>>   >>>
>>>   >>> _______________________________________________
>>>   >>> m2e-users mailing list
>>>   >>> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>  >>> 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>   >>>
>>>   >>
>>>   >> _______________________________________________
>>>   >> m2e-users mailing list
>>>   >> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>  >> 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>   >> _______________________________________________
>>>   >> m2e-users mailing list
>>>   >> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>  >> 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>   >>
>>>   >
>>>   > _______________________________________________
>>>   > m2e-users mailing list
>>>   > m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>  > 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>   >
>>>   >
>>>   >
>>>   > _______________________________________________
>>>   > m2e-users mailing list
>>>   > m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>  > 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>   >
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx> 
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@xxxxxxxxxxx <mailto: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
>> _______________________________________________
>> 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