Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: buildr-user@incubator.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 arkin@intalio.com does not designate 72.14.204.231 as permitted sender)
Message-ID: <3de5d7d20808131115j5cb5a904mc6ee91bdd19cb913@mail.gmail.com>
Date: Wed, 13 Aug 2008 11:15:07 -0700
From: "Assaf Arkin" <arkin@intalio.com>
To: buildr-user@incubator.apache.org
Subject: Re: specifying metadata for an artifact
In-Reply-To: <48A2DBFB.6060602@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48A2DBFB.6060602@gmail.com>

On Wed, Aug 13, 2008 at 6:04 AM, Ittay Dror <ittay.dror@gmail.com> wrote:
> Hi,
>
> How can I add metadata to an artifact spec so it can be used by plugins? (in
> my case the same artifact is used in different ways according to this
> metadata). I thought specifying the artifact as a hash would allow me to put
> keys that the plugin will use, but those specs pass through several stages
> of sanitation which leaves just the standard attributes.

A spec is an identifier of the artifact, much like a URL it tells you
how to locate the artifact, it doesn't tell you anything else about
the artifact.  Artifacts are designed around one particular naming
scheme, coupled to the way they're located in remote and local
repositories.

If you want to change the task itself, it's just a Ruby object that
you can easily extend or include other modules in there.

Assaf

>
> I'd appriciate your suggestions,
> Ittay
>
> --
> --
> Ittay Dror <ittay.dror@gmail.com>
>
>
>