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 antoine.toulme@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:sender:reply-to:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        b=tg8RQKJrgXSRqWxW3fLxDQ0N4NoitDKcxLGWREOYZOn4wqdWC9pH2kRDVvVVWpKzgF
         8LJKOCjbeDtipaw4eJ6NJIjYobEqjOrCqdZ63JM/wIfaBmMCH9FvKF3q+JywzpK2ATcz
         Dd6lEfec0E+6sJ0n3y4Qriw02BpW6A+j2aOnE=
MIME-Version: 1.0
Sender: antoine.toulme@gmail.com
Reply-To: antoine@lunar-ocean.com
In-Reply-To: <op.u118b4klxo3od7@pcbedglucas.bedford.progress.com>
References: <op.u118b4klxo3od7@pcbedglucas.bedford.progress.com>
From: Antoine Toulme <antoine@lunar-ocean.com>
Date: Mon, 19 Oct 2009 13:55:51 -0700
Message-ID: <f97124910910191355o5f556a53t4edf323d882ffe03@mail.gmail.com>
Subject: Re: installing non-archive artifacts
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=00504502d05dbb6e0f04764ff9f2

--00504502d05dbb6e0f04764ff9f2
Content-Type: text/plain; charset=ISO-8859-1

Hi George,
this is because you use the install task, which is extending the file task
of Rake.
That file task only runs if the file is not present.

You can try invoking the task to force it to execute:

(install task).invoke

Note that I didn't try this, and that I don't know off hand what the install
method returns. If that doesn't work, you'll need to find the install task
of that artifact in an other way.

Thanks,

Antoine


On Mon, Oct 19, 2009 at 11:29, 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
>

--00504502d05dbb6e0f04764ff9f2--