On 16/01/2011, at 1:33 AM, John Murph wrote: > On Tue, Jan 11, 2011 at 5:51 PM, Adam Murdoch <[email protected]> wrote: > > On 11/01/2011, at 10:19 AM, John Murph wrote: > >> What has replaced the --no-opt? > > All the incremental build bug fixes. > > >> I use it all the time (but I'm currently on 0.9). > > What do you use it for? > > > I'll often use it to force a task to execute even when Gradle considers it > "up-to-date". This is often to determine if the up-to-date is wrong. > Sometimes it's because something weird has happened and I just want to make > sure nothing is skipped. Sometimes it's because I'm working on a task (in > particular, getting inputs/outputs set up) and I made a mistake.
You could use the clean rule for all of these things, I think: gradle cleanMyTask -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
