Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of adam@clownsinmycoffee.net
 designates 69.89.17.193 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <460579CC.3070505@gmail.com>
References: <7edfeeef0703241202l3d3829ffm6477a66eee7ce3a6@mail.gmail.com>
 <460579CC.3070505@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <914EA9DF-5A22-4D36-B85C-7F01EF60741F@clownsinmycoffee.net>
Content-Transfer-Encoding: 7bit
From: Adam Constabaris <adam@clownsinmycoffee.net>
Subject: Re: i18n code build system
Date: Mon, 26 Mar 2007 00:08:12 -0400
To: abdera-dev@incubator.apache.org

This isn't directly related, but I do have a pom for the i18n  
dependency, which also requires patching the pom for the core  
subproject.  If nobody's yet done a build.xml, I'll take a look at  
generating one of those and submitting a patch.

cheers,

AC

On 24-Mar-07, at 3:19 PM, James M Snell wrote:

> +1. that's been on my todo list.  It wouldn't break my heart if  
> someone
> else got to it first ;-)
>
> - James
>
> Garrett Rooney wrote:
>> So, if the i18n code is going to be separate from the rest of Abdera
>> (i.e. we're planning on moving it out of the tree eventually)  
>> would it
>> be possible to extract its build logic from build/build.xml?  I was
>> thinking of updating my work-in-progress ivy patch today, but I don't
>> want to totally duplicate the current logic to build the i18n stuff.
>> It seems like we could just put a stupidly-simple build.xml in
>> dependencies/i18n, and since we are trying to make that code
>> independent it's going to need that eventually anyway...
>>
>> -garrett
>>