Project Structure and Layout Conventions
Contents
-
Directory structure. Naming should be followed precisely.
-
bin - output dir (TODO: ?? bin or build. Then nest under this specific directories for each build tool and for each output type e.g.:
- eclipse
- ant
- dist - packaged distributions
- lib - external libs kept locally
-
docs - documentation (note docs NOT doc, Docs, Doc etc)
-
internal - all internal documentation e.g. design, extra docs on api, code, uml ...
- user_guide
- src
-
test
- testdata
- examples
-
www - web stuff (TODO: or named website ???)
if we have src files other than java (e.g. xsl etc) then need further nesting under src and test as follows:
- java
- xsl
- ...
-
Each root directory should contain a build.xml file suitable for ant or nant. This should contain a basic standardized set of targets (see coding_conventions.htm for more detail).
(N)Ant Build File Organization
-
Target Names:
-
Consistent.
- Follows standard target naming conventions
-
clean (and sub targets thereof: e.g. clean.compiled-files)
- build
- dist
- prepare
Naming
-
LCU = lower case underscore
-
Tables
-
singular names
-
primary key names of form tablename_id