Thank you for your response. But it didn't solve my problem. I still don't get the new jar file, the only way to get it is to remove the old onefrom the gradle cache dir. This forces gradle to look in my repositories like my local .m2 directory. How can I tell gradle that it always should look for a new version of a dependcy even if the version number didn't change?
Thanks, Evert 2010/7/20 Jason Porter <[email protected]> > In the dependencies of the web project you can say something like > > runtime project(':core') > > that should do it for you. > > On Tue, Jul 20, 2010 at 14:28, Potje rode kool > <[email protected]> wrote: > > I am trying to build a multiproject but I got some problems. > > I have a core project that contains things like dao and service classes, > > another project web depends on core. > > When I change something in my core project and I call: gradle clean > > install war, the web project doesn't get the new jar from the core > project. > > I deploy to a local maven repro. I only get the new core jar if I delete > the > > jar from the cradle cache. > > Before gradle I used ivy from ant and there I could fix it by specify a > > changing="true" attribute on the core dependency. > > Is there a way to get something simular with gradle? > > > > Thanks > > > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net, pgp.mit.edu > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
