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 esmiley@ebrary.com designates
 209.85.215.44 as permitted sender)
MIME-Version: 1.0
Date: Wed, 21 Mar 2012 11:35:46 -0700
Message-ID: 
 <CA+i+dR0kBLpKF0jNn1HSKf+YmDY=2kKzpHFt1L-+i4Tdg=s27Q@mail.gmail.com>
Subject: Customizing repositories, methods of downloading artifacts
From: Ed Smiley <esmiley@ebrary.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=f46d040124e94d5dad04bbc50fbd

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

Hi All,

This is a somewhat open ended question.

I built a component for uploading  and downloading versioned components
using S3, which closely resembles the Maven spec (group/component/version
and type), although it supports directory trees as well as zip and jar
files.  Is it possible to extend the Buildr repository types, or add custom
code to a artifact in some fashion, so that the implementation would work
more or less transparently?

I have it working fine, but using custom methods.  I thought it would be
cooler if I could make it more transparent.

Thanks

Ed Smiley

--f46d040124e94d5dad04bbc50fbd--