Return-Path: <sr@adolos.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 98488 invoked from network); 31 Jul 2000 09:45:53 -0000
Received: from finch-post-11.mail.demon.net (194.217.242.39)
  by locus.apache.org with SMTP; 31 Jul 2000 09:45:53 -0000
Received: from adolos.demon.co.uk ([212.228.187.7] helo=PowerBookG3)
	by finch-post-11.mail.demon.net with smtp (Exim 2.12 #1)
	id 13JC8q-000EUD-0B
	for cocoon-dev@xml.apache.org; Mon, 31 Jul 2000 09:45:52 +0000
To: cocoon-dev@xml.apache.org
Subject: C2 Ant Classpaths assume xalan, xerces, avalon, etc.
Date: Mon, 31 Jul 2000 10:45:13 +0100
From: Stuart Roebuck <sr@adolos.com>
reply-to: sr@adolos.com
x-mailer: Apple Mail (2.317)
Message-Id: <E13JC8q-000EUD-0B@finch-post-11.mail.demon.net>
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

The current "build.xml" file for building Cocoon2 seems to assume that  
AvalonAware, jakarta-regexp, xalan, xerces & servlet are all in the default  
classpath.

Is it worth adding some properties for their locations in the release eg.:

    <property name="lib.avalon"  value="lib/AvalonAware.jar"/>
    <property name="lib.regexp"  value="lib/jakarta-regexp-1.1.jar"/>
    <property name="lib.servlet" value="lib/servlet_2_2.jar"/>
    <property name="lib.xalan"   value="lib/xalan_1_0_1.jar"/>
    <property name="lib.xerces"  value="lib/xerces_1_1_2.jar"/>

And then explicitly referencing them in the parts of the build that require them.

eg.

In "compile target":

    <javac...
	  ...
      <classpath path="${lib.avalon}:${lib.servlet}:${lib.xalan}:${lib.xerces}:$
{lib.regexp}" />
    </javac>

In "docs target":

    <java fork="yes"
          classpath="${java.class.path}:${doc.generator.package}:${lib.xerces}" 
          ... />

I'm not clear on what current wisdom advocates re: classpath  
referencing... My view is that projects should explicitly include  
classpaths because otherwise you build big dependencies into the overall  
environmental CLASSPATH and possible clashes where different projects  
require different versions of particular libraries.


Stuart.