Well that makes sense. Unless otherwise declared how would gradle know when your new task is up-to-date. Unfortunately I am still too new to know how a task can configured to declare "UP TO DATE". I have seen it when building Gradle from source. So hopefully someone answers but if not I would check what is happening there.
Jesse On Mar 11, 2010, at 10:41 AM, Andrey Adamovich wrote: > Hmm, the reason I ask is because I have introduced a new task for xmlbean > compilation. And I made it dependent on compile task: > > compileJava.dependsOn xmlbean > > But it seems that xmlbean generation is forced to be done every time I run > gradle build. And that also causes jar recompilation. > > Andrey > > From: Jesse Eichar <[email protected]> > To: [email protected] > Sent: Thu, 11 March, 2010 10:34:32 > Subject: Re: [gradle-user] Up-to-date > > I am also new to Gradle but I can say it does. I think it depends on the > type of task. For example generating a jar will only occur if one of its > dependencies has changed. > > Some aspects are still in the works. For example compilation still does more > work than necessary but that is slated to be fixed in the near future. > > Jesse > > On Mar 11, 2010, at 10:31 AM, Andrey Adamovich wrote: > >> Hi guys! >> >> I'm new to gradle. Does gradle support up-to-date check for tasks? E.g. if >> artifact is built already it skips the tasks unless you clean the artifact. >> >> Andrey >> >> > > >
