Module not rebuilding after build.gradle change
What I do: I keep build.gradle out of module directory, I change
it, run "gradle build".
Result: compileFlex UP-TO-DATE
Expected result: rebuid module
What do I do wrong?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Yennick Trevels on 20 Mar, 2014 09:53 AM
This is a discussion with some of the Gradle team members that I remember from two years ago, don't know if this issue still applies:
http://gradle.1045684.n5.nabble.com/Incremental-Build-and-build-fil...
I'll try to find some more information on whether this got fixed or not. Or you could post your question on the Gradle forums, maybe they know something more about it.
2 Posted by shamruk on 20 Mar, 2014 10:44 AM
Thanks. This issue is very important, it makes gradle completely unreliable. This way gradle builds something based on some modules built before but probably changed.
I have configured the build and was very surprised when some modules stopped working when other members of the team made minor changes in the code. Than I have restarted integration server and "gradle clean build", saw a lot of modules broken...
I have a filling that even "gradle clean" (without restarting the server) doesn't rebuild everything (but not sure).
Support Staff 3 Posted by Yennick Trevels on 22 Mar, 2014 02:04 PM
Here's another thread which discusses something similar. The consensus seems to be that, when you change something in your build file, you generally should run the clean task.
http://forums.gradle.org/gradle/topics/task_depending_on_build_grad...
4 Posted by shamruk on 25 Mar, 2014 05:50 PM
More links:
http://issues.gradle.org/browse/GRADLE-2936
http://issues.gradle.org/browse/GRADLE-1910
No solution yet.
Only workaround I can think of is generating md5 hash of *.gradle to corresponding source folder. Or generate md5 of all gradles and run "clean".
shamruk closed this discussion on 25 Mar, 2014 05:50 PM.