Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (nike.apache.org: domain of alex.boisvert@gmail.com
 designates 74.125.82.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <66872DA3F0544513BA7D6D5F050E09CB@gmail.com>
References: <3390B1A98B8A43D5AB90B6157F428DC6@gmail.com>
	<9B554F8383A84955B823580309DA575C@gmail.com>
	<CAHuk3y5JTD5uMxy0wjw+cksU11qKA=7Zm-mb2jVEFNsWU40Kug@mail.gmail.com>
	<66872DA3F0544513BA7D6D5F050E09CB@gmail.com>
Date: Wed, 2 Nov 2011 10:57:37 -0700
Message-ID: 
 <CAHuk3y717tPsxzjmVyU-Dueqkm5Hf=muTYZaDSDBW5O7-_gyBA@mail.gmail.com>
Subject: Re: Snapshot artifacts
From: Alex Boisvert <alex.boisvert@gmail.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=0016e6d646971bd64704b0c435bd

--0016e6d646971bd64704b0c435bd
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 2, 2011 at 4:46 AM, Dominic Graefen
<dominic.graefen@gmail.com>wrote:

> 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?
>

It's typically created by Maven during (snapshot) artifact deployment.
 Buildr does not currently update metadata.xml.

My problem with the update_snapshots option is that it always updates and
> therefore always forces a recompile of the whole project.
>

Please file a bug :(  ... and dig into it if you can!


>
> 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.
>

Ok.

alex

--0016e6d646971bd64704b0c435bd--