to automate this, a eclipse-plugin could hook into eclipse and do a 'gradle resources' when appropriate.
gradle should have some kind of embedded-mode to save startup-time then ... i think i have read about embedded-mode somewhere in the docs but don't remember where it was. Helmut Denk wrote: > > hi, > > > levi_h wrote: >> >> how do you (or other Eclipse users who might read this) handle the >> filtering case you described >> when you're running tests inside Eclipse? >> > > i do not have /src/main/resources or /src/test/resources > registered as eclipse 'Source-Folders'. > > if something changes in the resources i run gradle before > i run unit-tests inside of eclipse. > > i dont see another solution esp. if you use > transformed or filtered resources. > > have a nice day ! > -- View this message in context: http://www.nabble.com/copying-of-resources-tp19798564p19853302.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
