If you haven't yet, you might check out the Tomcat documentation. They have a fairly utilitarian approach.
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/source.html Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 8:51 AM To: [EMAIL PROTECTED] Subject: Structure of CVS Repository Hi all, I have had a look through the archive and was unable to find anything on this line, so I was hoping some of you can point me in the right direction. How should I structure my CVS repository for a J2EE project? Previously I set it up as: <module name> - design - doc - lib - src - ant - java - jsp - sql | - informix | - oracle - xml Where: design - held design documentation doc - documentation on how to use our code lib - held any thrid pary jars used src/ant - ant build scripts for ejb/jar/war src/java - java code src/jsp - the jsps that make up the module src/sql - build scripts for the database src/xml - xml descriptor file for ejb/war It worked well, but I'm sure there are some of you out there who have better systems and I would appreciate any advice. Thanks in advance IV [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
