Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-user@jakarta.apache.org
Reply-To: <brett@knightsofthenet.com>
From: "Brett Knights" <brett@knightsofthenet.com>
To: <ant-user@jakarta.apache.org>
Subject: RE: Need help on making a dynamic build.xml
Date: Tue, 19 Jun 2001 17:03:36 -0700
Message-ID: <000c01c0f91c$74a75de0$0201a8c0@knightsAPC.knightsofthenet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6DDA62170439D31185750000F80826AC0668452A@zmerd004.ca.nortel.com>
Importance: Normal

This looks like something you could accomplish pretty easily with a script.

Based on your directory structure your script would:
create a copy task to send the files to be jarred to a working area
create a jar task to do the work. (you actually might be able to get away with just scripting a jar task)

HTH

> -----Original Message-----
> From: Jay Glanville [mailto:dickon@nortelnetworks.com]
> Sent: Tuesday, June 19, 2001 7:25 AM
> To: Ant-User (text)
> Subject: Need help on making a dynamic build.xml
> 
> 
> Perhaps calling this a "dynamic build.xml" is slightly 
> incorrect.  But let
> me tell you my situation before we worry over the semantics 
> of the title of
> the problem.
> 
> Basically, what I want to do is base what I deliver, and 
> where I deliver it
> to, on the directory structure of my source code.
> 
> For example, if my package/directory structure looks like this:
>   com.company.product_a.deliv_one
>   com.company.product_a.deliv_two
>   com.company.product_a.deliv_three
>   com.company.product_b.deliv_four
>   com.company.product_b.deliv_five
>   com.company.product_b.deliv_six
> 
> after compiling all the source code, I want to jar everything 
> at the 4th
> level (the deliv_ level) into a jar with the name of that 
> level, into a
> directory based on the third level (the product_ level).
> 
> Therefore, I want the resulting output of the above directory 
> structure to
> look like this:
>     output/product_a/deliv_one.jar
>                  .../deliv_two.jar
>                  .../deliv_three.jar
>     output/product_b/deliv_four.jar
>                  .../deliv_five.jar
>                  .../deliv_six.jar
> 
> If I could make a generic build.xml file based on this 
> philosophy, then
> designers can create new products and deliverables without 
> having to modify
> the build.xml file.
> 
> So, does anybody have a suggestion on a way to do this?
> 
> 
> --
> Jay Dickon Glanville
> P068 - SiteManager Development, Nortel Networks
> 613-765-1144 (ESN 395-1144)
> MS: 045/55/A05
> E-Mail: dickon@nortelnetworks.com
> 
>