Hola a Todos: ( I have built JetSpeed only some comments to the build process as it's designed now ) It's a pain to have a bin dir commited in the CVS repository , make difficult to do a cvs update -P -d of the entire jetspeed module without a prior " ant clean "... I have a System Install of ant as i use it in my own projects.. have needed to modify the build.xml file to suit my ant use, i do not use the custom build.bat, so when trying to build jetspeed the ant.home variable is not pointing to jetspeed own ant install.., junit.jar is not found this way.... ( this was easy to solve ).. I consider that it's no the best practice to include a pivate ant install.., at least you will need to respect the user self-managed environment in case he has one.. like me.. Another issue is that i found strange the requeriment of a bunch of properties defined ( junit.jar cactus-xx, etc )... to no use them at all when constructing the classpath ..;) Apart from that caveats everything goes fine i'm about to deploy my new freshly built jetspeed on 3.3 .., probably more comments soon :) Saludos , Ignacio J. Ortega --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
