Hi,
now that we are on subversion, this offers us the opportunity to
finall decouple the development of the various parts of Torque.
I'd propose that we reorganize the SCM to reflect this:
db/
torque/
runtime/ <----- trunk
trunk/
tags/
branches/
generator/ <----- trunk/src/generator
trunk/
tags/
branches/
templates/ <----- trunk/src/generator/src/templates
trunk/
tags/
branches/
plugin/ <----- trunk/src/maven-plugin
trunk/
tags/
branches/
common/ <----- stuff that all the parts use,
can be pulled in the projects using
svn:external
site/ <---- A wrapper site like the db-site or
turbine site to allow us havingmultiple
release versions and common information
in one place
trunks/ <---- A "checkout" directory like the
jakarta-commons has with "trunks-proper"
The idea is to remove all the "build" tricks from the current tree and
allow us to decouple the building of e.g. the generator and the
runtime. With the generator being able to build other templates (like
OJB) it is IMHO a good thing to be able to cut revisions independently
from the runtime.
Opinions?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
