Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4155E58A.6040406@latte.harvard.edu>
Date: Sat, 25 Sep 2004 17:39:22 -0400
From: "Mark R. Diggory" <mdiggory@latte.harvard.edu>
Reply-To: mark_diggory@harvard.edu
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [general] Do we need to support Ant based builds?
References: <9C5166762F311146951505C6790A9CF80229C1FF@US-VS1.corp.mpi.com>
	 <16d6c62004092214513b7eb81b@mail.gmail.com>
	 <f8b39ace040924084361c365f2@mail.gmail.com>
	 <415449FB.7030808@latte.harvard.edu> <4154B767.7000702@apache.org>
 <16d6c62004092512112dd91eae@mail.gmail.com>
In-Reply-To: <16d6c62004092512112dd91eae@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Martin Cooper wrote:
> A few quick comments:
> 
> 1) Not all Commons components are set up for Maven builds, so the
> "just a matter of" doesn't apply in all cases.

This is true, but all Commons projects are required to use Maven to 
build the Project's Website. It benefits a Commons project to use Maven 
to build and test the distributions and a majority of them do. Do we 
have a clear list of the projects that do not at this time?

My earlier point was strictly to bridge this "gap". All projects (Maven 
Based) can easily produce an Ant build.xml file using maven's Ant task, 
the build.xml file works correctly with Craig's current nightly build 
process, so Ant is the common denominator here and this solution is 
already "inadvertently" in production. Clearly it works.

> 2) The Commons nightly builds are just one part of the wider Jakarta
> nightly build, and certainly not all Jakarta projects use Maven, or
> are likely to do so any time soon.

True.

> 3) To answer the last question above - yes, we want nightly builds. I
> don't think we want to load up the Apache infrastructure with
> continuous commit-triggered builds for all of the Jakarta projects, or
> even just for Commons components. Having a nightly build gives us a
> predictable load at a known time.
> 
> --
> Martin Cooper
> 
> 
> 
>>Cheers,
>>Brett
>>
>>
>>
>>Mark R. Diggory wrote:
>>
>>
>>>At least in Maven, the "version" of the dependency is captured in the
>>>metadata of the project.xml file. When the ant build file is generated
>>>off the project.xml file, these dependencies are translated into the
>>>"get" url's to point at the ibiblio maven repository.
>>>
>>>    <get dest="${libdir}/commons-logging-1.0.3.jar"
>>>usetimestamp="true" ignoreerrors="true"
>>>src="http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.3.jar">
>>>
>>>    </get>
>>>    <get dest="${libdir}/commons-discovery-0.2.jar"
>>>usetimestamp="true" ignoreerrors="true"
>>>src="http://www.ibiblio.org/maven/commons-discovery/jars/commons-discovery-0.2.jar">
>>>
>>>    </get>
>>>
>>>So, in a sense, maven is already handling the correct dependencies
>>>both in the project.xml and the generated ant build.xml.
>>>
>>>-Mark Diggory
>>>
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org