Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: domain of alex.boisvert@gmail.com
 designates 209.85.219.212 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=uMCLEUcERTXVry9haxqpggjVLlEspkGHACLnta7N6LPKJzv11azHzxD8nK/EVdo8VR
         6CLDzENeJUsWeHcJNH7fJmkl4+zEyzI6wq26Uo+dhZLy/ykn+4EQdnOorJg1VH6xB4PP
         XoqNT4uj7BqoIMpOsLtLRYfqoLu+8zb7v6q9c=
MIME-Version: 1.0
In-Reply-To: <op.u118b4klxo3od7@pcbedglucas.bedford.progress.com>
References: <op.u118b4klxo3od7@pcbedglucas.bedford.progress.com>
Date: Mon, 19 Oct 2009 14:39:37 -0700
Message-ID: <4dcd15a90910191439m1781cddey8a1a7f0f42a8f0da@mail.gmail.com>
Subject: Re: installing non-archive artifacts
From: Alex Boisvert <alex.boisvert@gmail.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=0016e6da7de31203be04765095ac

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

I think that's a bug in the install task.  It should re-install even if the
target already exists (same as upload) to follow existing Maven conventions.

alex


On Mon, Oct 19, 2009 at 11:29 AM, Greg Lucas <greg.lucas@gmail.com> wrote:

> I've got a build that needs to install/upload an XML file as an artifact.
> I'm doing the following in my Rakefile:
>
> # produce the XML file
> filter('src/...').into('target/...').using(...)
>
> # define an artifact and hook in to install/upload
> xml_artifact = artifact(...).from('target/...')
> install xml_artifact
> upload xml_artifact
>
>
> This works fine the first time, but any subsequent time a run the build the
> artifact is never updated in my local m2 repo. It looks like install only
> works if the artifact is not already there. That's not consistent with the
> behavior using package.
>
> I suppose I could define a new packaging type for this but that seems like
> overkill. Is this the intended behavior of install? Is there a better way to
> deal with artifacts that are not in fact packaged archives?
>
> I'm using buildr 1.2.10 (as currently dictated by the Apache ODE 1.x
> branch).
>
> --
> Greg Lucas
>

--0016e6da7de31203be04765095ac--