Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-user@jakarta.apache.org
Message-ID: <F103AA23EB20D2119ACE00805FF7BD0D0323EB3C@g4ntex3.etrade.com>
From: Christopher Berry <christopher.berry@etrade.com>
To: "'ant-user@jakarta.apache.org'" <ant-user@jakarta.apache.org>
Subject: RE: perl scripts for tomcat.
Date: Wed, 6 Jun 2001 16:58:34 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

That's not necessarily true. I don't need a (separate) install of Perl
anymore than I need an install of Ant, right? Look at how Tomcat is
distributed. It contains the distributable parts of Ant, and does not
require an install. I can do the same for Perl. The simple launch scripts
would reference /tools/perl/win32 or /tools/perl/unix depending on BAT or
SH. 

What makes this advantageous is that I only have to maintain a single "real"
script. (i.e. one w/ meat in it) -- that can be used on any platform. 

Cheers,
-- Chris

> -----Original Message-----
> From: debic@epiphany.com [mailto:debic@epiphany.com]
> Sent: Wednesday, June 06, 2001 3:24 PM
> To: ant-user@jakarta.apache.org
> Subject: RE: perl scripts for tomcat.
> 
> 
> > It seems to me that homogenizing the scripts to Perl, coupled 
> > with simple, one line, OS-specific launch scripts, would make life 
> > simpler. (At least for us, since we must support both OS flavors..)
> > 
> I tend not to agree, this forces you to install Perl on each 
> supported 
> platform.
> 
> At my site we use Tomact/Java servlets to drive a build 
> interface to the
> build 
> process. Since our product is mostly Java and the build is 
> driven by Ant the
> JDK's 
> are already present on each platform. As for Perl, the XML 
> build script/Java
> Tasks
> combination works better, and if I need Perl's rich pattern 
> manipulation
> capabilities
> I turn to the ORO package which supports oobject operations 
> using Perl (and
> regex and sed)
> expressions in Java code.
> 
> Best regards.
>