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> 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] 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] On Behalf Of Igor Fedorenko > Sent: 11 July 2012 12:53 > To: 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] On Behalf Of Igor Fedorenko >> Sent: 11 July 2012 12:04 >> To: 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] *On Behalf Of *Markus Karg >>> *Sent:* 09 July 2012 15:13 >>> *To:* 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 >>> 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 _______________________________________________ m2e-users mailing list m2e-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/m2e-users
|