On 16/04/10 11:52 PM, Steve Appling wrote:
In addition to your task dependency issues, I think you are running into the
bug GRADLE-909. The cached information for the UP-TO-DATE checks is unreliable
and running a clean will not necessarily cause a compile (even if across two
different invocations as you show). You will have to either re-run with the -C
rebuild option to rebuild the cache
You have to use the clean task at the same time as -C rebuild, otherwise
it won't unstick the cache, ie use gradle -C rebuild clean
You only need to do this once. Once it's unstuck it will be fine.
It gets stuck when you:
- use a new version of Gradle on an already built project, without
running clean
- use -C rebuild on an already built project without running clean
- Delete the .gradle directory of an already built project without
running clean
I will fix this soon.
or use the --no-opt option to disable the up-to-date optimizations.
On Apr 8, 2010, at 2:19 AM, Geronimo M. H. wrote:
What I don't understand:
- after running clean, how could compileJava be up-to-date?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
