On Sun, Sep 30, 2012 at 11:46 AM, Luke Daley <luke.da...@gradleware.com>wrote:
> > On 25/09/2012, at 1:50 PM, Guillaume Laforge wrote: > > > Hi all, > > > > I noticed a strange behavior with the "install" task, when I'm using it > on the Groovy project. > > In a nutshell, it's not updating the JAR in my local repo, unless I'm > doing a "clean install". > > > > Let's say I'm modifying something in the groovy-servlet subproject. > > Then do "gradle install". > > The changes I made don't find their way in the snapshot (I'm don't even > know if it scratches the old jar or not). > > How do you know that it's not updating? > Because when I then use that JAR, the modifications I had made are not there. For example, say I'm adding some println statements here and there, and when I use the supposedly updated JAR, my printlns aren't there. But when I do a clean install, I get those new printlns. > > Although I see that the compiler does indeed compile my changes, as for > example, if I introduce a typo on purpose, the compiler will complain. > > But it's only when I do "gradle clean install" that the snapshot is > updated with my changes in my local repo. > > > > So... is it a problem of the Groovy build, or a problem in Gradle? > > If the latter, is it a known issue? > > > > It is quite annoying as clean builds are more time consuming :-( > > I'm unable to reproduce this with a different project. I tried with the > Groovy project, but `install` fails with https://gist.github.com/3806353 That's because you're using an old 1.8.x project setup that had some generated sources, but it's working differently now with the 2.x line. You should do a clean checkout of Groovy and start anew. -- 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>
