On Wed, 2004-11-17 at 07:17 +0000, Henning P. Schmiedehausen wrote:
> Daniel Rall <[EMAIL PROTECTED]> writes:
>
> >I'd be happy moving only those projects. Maven has had some degree of
> >Subversion support for quite some time (available by wrapping the
> >commandline binaries), but as to the specific functions referenced by
> >Henning, I am not certain of the support. If it's missing, I'm willing
> >to add it for Subversion.
>
> Cool. Then I'm all for it. What time frame do you propose?
I'm ready any time. You and Eric give the word, as you two are
producing the most code churn ATM.
Regarding layout, here's a strawman to nitpick which makes the
assumption that neither the site module nor most of the other modules
are in use:
jakarta/
fulcrum/
branches/
tags/
trunk/
jcs/
branches/
tags/
trunk/
turbine/
branches/
2.2/ <-- branches from the jakarta-turbine-2 module
2.3/
3.0/ <-- the tip of the jakarta-turbine-3 module
tags/
historical/ <-- the tip of the jakarta-turbine.old module
trunk/ <-- the tip of the jakarta-turbine-2 module
This layout assumes that Fulcrum and JCS will eventually fully decouple
from Turbine and become its own full-fledged Jakarta project, a
repository of useful Avalon services. "historical" could alternately be
called "ancient".
Fortunately, with Subversion, we can change this layout after importing
if we run into an "Oops!".
For your reference, here's the list of existing CVS modules:
[EMAIL PROTECTED]:cvs$ ls -d *turbine*
jakarta-turbine-2/ jakarta-turbine-orgami/
jakarta-turbine-3/ jakarta-turbine-site/
jakarta-turbine-component/ jakarta-turbine-stratum/
jakarta-turbine-flux/ jakarta-turbine-tdk/
jakarta-turbine-fulcrum/ jakarta-turbine-tdk.old/
jakarta-turbine-jcs/ jakarta-turbine-torque.old/
jakarta-turbine-jyve/ jakarta-turbine.old/
All modules would be marked read-only after the conversion.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
