Hi,
I think we agreed that we want to move to using a standard
build.xml file, but there are some other things we should
discuss.
Using a standard build.xml file would allow people to use
their installed version of Ant and the set of jars they
choose to make available to Ant.
I have personally started using an installed version of
Ant and I place all the jars I need for building in the
$ANT_HOME/lib directory. I have actually found this to
be a lot easier when building multiple projects.
What do people feel about trying to move our build
system toward using an installed version of Ant? The first
move would be removing the ant jars, and hopefully when CJAN
works eventually removing all the jars.
I just wanted to start a discussion. For now, simply
renaming build-turbine.xml to build.xml will allow the
scripts to work as per usual and allow people with installed versions
of Ant to build turbine.
I have always liked having jars in CVS for ease of
use, but I think that if for every project I built
kept all required jars in CVS I would have 50 copies
of Ant and Xerces lying around. Until something like
CJAN is working I wouldn't want to remove all the jars.
But I think moving in the direction of removing jars
from CVS and using something like CJAN is the right
way to go.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
