Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 75702 invoked by uid 500); 6 Jun 2001 20:28:57 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 75559 invoked from network); 6 Jun 2001 20:28:54 -0000 Message-ID: <38A6C7D1B5A8D4118D5B00508B5E08E30165F2D0@goofy.epiphany.com> From: debic@epiphany.com To: ant-user@jakarta.apache.org Subject: RE: perl scripts for tomcat. Date: Wed, 6 Jun 2001 13:24:15 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > 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.