----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 13, 2001 6:29 PM Subject: cvs commit: jakarta-commons-sandbox/cjan README.txt > sanders 01/04/13 09:29:21 > > Added: cjan README.txt > Log: > Initial thoughts of CJAN ;-) > > Revision Changes Path > 1.1 jakarta-commons-sandbox/cjan/README.txt > > Index: README.txt > =================================================================== > CJAN - April 12, 2001 > > Ideas conceived by many parties > Formalized and coded by: > Scott Sanders <[EMAIL PROTECTED]> > > > Java is an excellent platform for creating cross-platform code. One small hack > of the Java platform is the CLASSPATH. CJAN intends to ease problems associated > with the classpath as well as binary files in development CVS trees, by allowing > build systems such as Ant to dynamically download/cache/include various > dependencies. No longer will the typical open-source developers setup include > 37 copies of ant.jar, 5 different xerces.jar, 3 incompatible xalan.jar, and not > a single useful turbine.jar. > > The idea is akin to CPAN (http://www.cjan.org) in that various binary packages, ooops. Little typo here. Should read http://www.cpan.org (I wanted to correct it in CVS but for some reason cannot update the sandbox on my machine right now). > most likely in the form of .jar files, will be made available over the internet, > so that they can be downloaded and cached by a tool such as Ant. > > CJAN will consist of one or more optional Ant task(s), as well as many XML-based > repository and module definition files. The intent is that the Ant build for a > particular project will be able to list dependent .jar files, and download any > that are missing. Thus binary files will not need to be checked into CVS and > constantly updated, and the world will be generally happier overall, we hope ;-) > Thanks Vincent
