info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Structure of CVS Repository


From: Daniels, David
Subject: RE: Structure of CVS Repository
Date: Thu, 14 Mar 2002 08:59:57 -0600

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: address@hidden [mailto:address@hidden
Sent: Thursday, March 14, 2002 8:51 AM
To: address@hidden
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

address@hidden

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



reply via email to

[Prev in Thread] Current Thread [Next in Thread]