> Is there any reason that the ant.jar and xerces-XXX.jar can not be put into
> the /lib directory of the tdk with the junit-3.2.jar? I think this will make
> the TDK more self-contained meaning that the classpath set in the build
> files could be changed to this:
>
> set
> CLASSPATH=../lib/ant.jar;../lib/xerces-1.1.3.jar;../lib/junit-3.2.jar;%JAVA_
> HOME%/lib/tools.jar
>
> so that the likelihood of having to edit the build files is reduced, thus
> causing less confusion for new users.
>
There's the rub - the TDK isn't meant to be built by new users. New users aren't
expected to grab the TDK source from CVS; they're meant to download a packaged
TDK binary. Making the TDK easier to _build_ is not necessarily a design goal;
making the TDK easy to _use_ is.
In addition, we don't want to duplicate those jars in CVS. The TDK isn't meant
to be self-contained; its build process requires that you have the turbine
source checked-out in tandem.
> another thing i noticed is that the build also seems to need the xml.jar
> file somewhere in its classpath or am i mistaken? if not, could we include
> this also?
>
It shouldn't need xml.jar. Old versions of Ant required this for the javax.xml.*
interfaces. However, this file has been deprecated by JAXP, and modern versions
of Xerces (i.e., >1.1.2) include these interfaces in the jar. Where are you
seeing references to it?
> -scott-
>
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
