|
From: Liam M. <lm...@WP...> - 2001-08-06 20:16:01
|
Yep, I noticed :o) first.. we don't use "CVS" per se at EMC, but we use a larger more robust system (with plenty of hassles nonetheless) called "ClearCase". It's proprietary. We do have a lib folder in our development branches, and in this folder are included jar files from 3rd party software we are licensing (for example, classes for DB Mapping 3rd party software, classes for Java GUI 3rd party software, as well as the oracle drivers for database connectivity). I'm planning on checking out Cocoon's source from CVS to see how they do it. If they include 3rd party stuff, I see no reason why we shouldn't. If they don't, well then we don't have to either :o) but it's not a bad idea.. that's what the repository is there for. 2nd, I've already just about finished a batch file for Ant building, copied almost word for word from Cocoon's batch file (except modified to include relevant jars). It requires a %TOMCAT_HOME% env variable (it expects that you're putting the jar files in your classpath dynamically by adding them to the tomcat folder), as well as a lib folder that houses ant and ant-optional. If we do decide to package jars with CVS, then the TOMCAT_HOME requirement becomes unnecessary. Of course adding duplicated files to CVS does increase the size of the tarball, but I'm not too worried - yet. 3rd, I've thought about creating an installation kit, but I don't think it should be any more robust than Cocoon's installation "kit" (however, we better have much better documentation). We certainly don't need an executable like Apache's installation. I'll start working on something as soon as the heirarchy of the CVS tree has become closer to finished. ------- Liam Morley "light the deep, and bring silence to the world. light the world, and bring depth to the silence." |