Hi I actually have backed out of this approach for now, can't see how I can easily create a (distributable) repository structure.
I'll rely on the current ant/ivy scripts to create the assembly (I should be able to use the ivy ibiblio resolver), invoked using gradle of course. When(if) the upload with dependencies feature comes in soon I might use it, but hopefully we will solve our packaging some other way - especially after having ant fully replaced by gradle :) thanks again. gretar On Fri, Oct 29, 2010 at 12:45 AM, Adam Murdoch <[email protected]> wrote: > > On 28/10/2010, at 8:52 PM, Gretar Arnason wrote: > > Thanks Adam, > > The approach is actually to reproduce a current method (which uses ant/ivy > to do similar things) but using gradle. > I see the ant->gradle shift as a stepping stone to 'greener' pasture, > mainly more modularization with our codebase. > > > In light of your comments I'll probably opt for setting up the assembly as > a 'real' (flat file) repository. > BTW, when using local file repository does it copy all the artifacts to the > cache, if so is there any way to prevent that and just reference the > artifacts in place? I would want to avoid the duplication of jars. > > > It's not supposed to copy them into the cache, but I suspect that it does. > > > > Also where can I find information on the Gradle daemon, sounds like an > interesting thing :) > > > Here: http://gradle.codehaus.org/Gradle+Build+Daemon > > At the moment, you use a special distribution. It contains a 'gradle' > command that you use exactly the same way as the normal 'gradle' command. > This command takes care of launching and using the daemon transparently > (actually, it's not that transparent - the daemon is much, much faster). > > You can download it here: > http://gradle.artifactoryonline.com/gradle/webapp/browserepo.html?pathId=distributions%3Agradle-snapshots%2Fgradle-0.9-rc-2-build-daemon-bin.zip > > Feel free to try it out. Be aware that the daemon is an experimental > feature at this stage. There are still some issues with it. It works well > enough on unix for day-to-day development. There are still some file locking > problems on windows. I suggest you don't use it for your CI builds. > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > CTO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > >
