CVS seems to work. I added the README to see if it works like I
expected, and I should be on familiar ground for the time being.
The next question is what the directory structure should look like.
Please have a close look at my jarchive and tell me what should be
placed where. I don't think this should be changed every other week,
so be better take extra care.
There is no drug known to man which becomes safer when its
production and distribution are handed over to criminals.
From: Nick Pilon <npilon@is...> - 2003-05-11 16:32:38
On March 27, 2003 9:56 pm, Thorsten Haude wrote:
> CVS seems to work. I added the README to see if it works like I
> expected, and I should be on familiar ground for the time being.
Yup, got this working.
> The next question is what the directory structure should look like.
> Please have a close look at my jarchive and tell me what should be
> placed where. I don't think this should be changed every other week,
> so be better take extra care.
My personal preference (based on experience with other projects) is something
src/ - this is the root of all package directories, where we compile from.
classes/ - this is actually on the classpath, and where we compile to.
docs/ - documentation goes here.
jars/ - Built packages go here. This directory doesn't exist in CVS, but
is created as necessary.
libs/ - Library JARs go here. This is also on the classpath, and DOES
exist in CVS.
Then we have a build.xml (for ant) in the CVSROOT) with targets for building
classes, building JARs, and building documentation.
Since we're going to be all-Java, I don't think there'll be any problems with
this. Though we might want to consider a data/ or xml/ directory for XML
data-files and XSLT stylesheets.
Urgh. I do NOT believe how busy April got. >_<
"The purpose of abstracting is not to be vague, but to create a new semantic
level in which one can be absolutely precise."
-Edsger Dijkstra, 1930-2002
Get latest updates about Open Source Projects, Conferences and News.