Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates
 205.152.59.65 as permitted sender)
Message-ID: <43911C0E.5030504@bellsouth.net>
Date: Fri, 02 Dec 2005 23:16:14 -0500
From: Alex Karasulu <aok123@bellsouth.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
MIME-Version: 1.0
To: felix-dev@incubator.apache.org
Subject: Re: Repository/package structure
References: <438E1142.2060302@ungoverned.org> <438F8530.9090209@interfree.it>
 <43906165.2020806@ungoverned.org> <4390A3C2.1030403@toolazydogs.com>
 <4390BAFB.4080701@ungoverned.org> <4390EC9D.8010800@toolazydogs.com>
 <4390F2B9.9010905@ungoverned.org>
In-Reply-To: <4390F2B9.9010905@ungoverned.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Richard S. Hall wrote:

> Alan D. Cabrera wrote:
>
>> I think that it's great to have it all packaged up in the manner you 
>> described; this can be accomplished with the maven assembly plugin.
>
>
> Yes, I expected that our eventual maven build process would do it.
>
>> I think that it's bad form to support both ant and maven.
>
>
> I don't. But if it is a problem, Felix release could ship only with 
> ant support and maven could just be used for Felix developers.

I agree with Richard here.  We can have both.  Maven can generate ant 
build.xml files too btw but there's nothing stopping us from having both 
the ant and maven stuff maintained independently and side by side.  Lots 
of work though.

> To make sure that I am being clear, I am not talking about having two 
> build processes for the entire Felix project. I anticipate that the 
> Felix project will ultimately only have a maven build process. But the 
> release archive of the framework will be self-contained and include an 
> Ant build file (and a maven one if it isn't problematic).

Should not be a problem.

Alex