Thanks Peter for the response. I will keep this in mind. On Fri, Jan 20, 2012 at 12:05 PM, Peter Niederwieser <pnied...@gmail.com>wrote:
> > Jason Hatton wrote > > > > Before I was using a doLast on the eclipse task but, that doesn't work > > anymore in version 1.0.7. > > > > This should still work except that you now have to do `tasks.eclipse.doLast > {}` rather than just `eclipse.doLast {}`. This is because `eclipse` now > refers to a model object used to configure the Eclipse task(s). In other > words, you typically don't configure the Eclipse tasks directly anymore. > > In general, a better approach is to have your own task(s) and make the > `eclipse` task depend on them: > > tasks.eclipse.dependsOn(myEclipseTask) > > The only downside to this approach is that you cannot control the order in > which the Eclipse tasks run. Usually this won't be a problem. > > -- > Peter Niederwieser > Principal Engineer, Gradleware > http://gradleware.com > Creator, Spock Framework > http://spockframework.org > Twitter: @pniederw > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Best-Practices-on-extending-Eclipse-file-generation-tp5161066p5161264.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 > > >