>> Also requiring a net connection to do every build is a >really bad idea >> IMO - there are plenty of valid reasons why folks might want >to do work >> without the network. This also goes for being >cross-platform: we need >> to support users on Windoze as well as the unixes of the world so I >> think it is important to include .bat files in most cases >where we have >> .sh scripts for bootstraps, etc. (But that's a different issue...) >What about having each needed jar as a property, and have a >setup task check >if those file are effectively present, and if not, downloading >them for a >known location ?
+1, that's how for example Tomcat 3.3 and 4.x allow you to build them, defininig regexp, javamail, jndi, jta jar locations.... --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
