I looked in the source and found that it is checking for updated snapshots via a maven-metadata.xml which contains the latest update timestamp. But I don't have that metadata file, is that something my repository (nexus) should create?
My problem with the update_snapshots option is that it always updates and therefore always forces a recompile of the whole project. Therefore I don't think it needs to be available as a setting in the yaml file, and would rather find a way to have snapshots only update when they are newer than in my local repository. -- Dominic Graefen Freelance: Interactive Developer / Creative Technologist devboy.org On Tuesday, November 1, 2011 at 3:00 PM, Alex Boisvert wrote: > There's no shorter way currently. We could make it a `setting` instead of > an application option, in which case it could be set via > $USER/.buildr/settings.yaml or build.yaml next to the buildfile. Would > that be better? > > alex > > > > On Tue, Nov 1, 2011 at 5:53 AM, Dominic Graefen > <dominic.grae...@gmail.com (mailto:dominic.grae...@gmail.com)>wrote: > > > Just found: > > > > Buildr.application.options.update_snapshots = true > > > > Is there a shorter way of setting options inside a buildfile? > > > > > > On Tuesday, November 1, 2011 at 12:59 PM, Dominic Graefen wrote: > > > > > Hey Guys, > > > > > > I couldn't find any info on this in the docs: Does buildr have > > update-policies for SNAPSHOT artifacts? > > > Right now my Snapshot artifact is not overwritten by a newer build, > > > > anyway I can force it to? > > > > > > Cheers, > > > > > > -- > > > Dominic Graefen > > > Freelance: Interactive Developer / Creative Technologist > > > devboy.org (http://devboy.org) > > > > > > > > > >
