Hi Carsten, The new build system was finished yesterday, and still needs testing, but I think even in it's untested state you'll have more success than with the old system. I can go from a fresh CVS checkout to having an avalon-excalibur.jar, by just typing 'ant' in the root. The external deps (jmx, altrmi) only need be specified if you want those components, which you won't if you're building for Cocoon.
To try it, run 'source depchecking.sh' in the root. On Tue, Apr 02, 2002 at 11:55:49AM +0200, Carsten Ziegeler wrote: > Hi, > > sorry if this is a dumb question - I wasn't able to follow all the > discussions over the last weeks. > > But is anyone able to build excalibur from scratch without big > modifications? > I delete the excalibur directory and made a fresh check-out. > > Then I installed the commons-altrmi (jakarta-commons-sandbox), junit, jmx > package like they were referenced in the sample ant.properties file. I > renamed the ant.properties.sample file to ant.properites and corrected the > base-path. So everything should be fine... > > But unfortunately during the build of the "all" package no SAX classes were > found. I fixed this by copying the xml-apis.jar to all/lib, but then next > errors occur. Another bug.. the ../jakarta-avalon/tools/lib/xerces-1.4.4.jar we rely on doesn't contain org.xml.sax.* any more. I've just fixed it in the depchecking branch. > So did I simply oversee something or is the build system not yet ready? It's not in the CVS head. 'source depchecking.sh' and be our guinea pig :) After this, javac build failures should be a thing of the past. --Jeff > Carsten > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
