On Sun, Sep 30, 2012 at 3:03 PM, Luke Daley <luke.da...@gradleware.com>wrote:
> [...]
>
If there was a problem where changes that were made to Groovy files were
> not picked up on compilation, we'd definitely know about it. Everyone would
> have the problem. Therefore, the fact that the jar in the build is the same
> as what is in the maven local cache is a good indicator that the change has
> been applied.
>
So... I've tried again, and I think the problem somehow lies with our
subprojects in a way or another.
Do the following:
1) gradle clean
2) gradle install
3) java -cp
~/.m2/repository/org/codehaus/groovy/groovy-all/2.1.0-SNAPSHOT/groovy-all-2.1.0-SNAPSHOT.jar
groovy.json.JsonBuilder
Since there's no main() method on JsonBuilder, it'll complain about that
method being absent
4) go to the groovy-json subproject, and modify JsonBuilder to add a dummy
main() method which does a println("hello")
5) gradle install
6) java -cp
~/.m2/repository/org/codehaus/groovy/groovy-all/2.1.0-SNAPSHOT/groovy-all-2.1.0-SNAPSHOT.jar
groovy.json.JsonBuilder
This time again, it'll complain again because there's no main method!
Although you've just added one!
So it's somehow a problem with the multimodule support.
It may very well be a problem in our build, and not at all in gradle, but
whatever it is, it's painful :-)
--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware
Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> /
Google+<https://plus.google.com/u/0/114130972232398734985/posts>
