Daniel Rall <[EMAIL PROTECTED]> writes:
>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.
Hi,
(back from ApacheCon, catching up with my mails...)
>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/
This is for Eric to say, personally I'd prefer
jakarta/
fulcrum/
component1/
branches/
tags/
trunk/
component2/
branches/
tags/
trunk/
component3/
branches/
tags/
trunk/
because else the tags directory will sooner or later filled with
literally hundreds of tags (foo-service-1.0, foo-service-1.1,
bar-service-1.0 and so on). I'd also like to decouple the various
components stronger which is easier (IMHO) if we don't have
trunk/
component1/
component2/
component3/
however, the reactor build might need this structure. Eric?
> jcs/
> branches/
> tags/
> trunk/
No call on that, however it seems that the JCS developers don't get
their act together on proposing for becoming a direct Jakarta
sub-project (come on folks! This is already an (almost done) deal. You
only need to send in your proposal!)
> turbine/
> branches/
> 2.2/ <-- branches from the jakarta-turbine-2 module
> 2.3/
> 3.0/ <-- the tip of the jakarta-turbine-3 module
I'm not happy with the 3.0 version tag. jakarta-turbine-3 is basically
a failed attempt at what Eric seems to get right with Turbine 2.4. I
don't want to block the innovation by having a "3.0" version that IMHO
will never get a release but will always be perceived as "newer" than
the Turbine 2.x release.
How about
turbine/
branches/
OLD/
turbine-2 <- Branches from jakarta-turbine-2
turbine-3 <- Branches from jakarta-turbine-3
2.3/
> tags/
> historical/ <-- the tip of the jakarta-turbine.old module
Where is this module? It is not visible at http://cvs.apache.org/viewcvs.cgi/
> trunk/ <-- the tip of the jakarta-turbine-2 module
-0. The problem with "trunk" is, that we don't have an uniform
"turbine" project. I definitely want to decouple META from the
HEAD/trunk and I have e.g. the ApacheFaces app as an example
application which I want to keep in the Turbine repo.
And also from Fulcrum, there are a few turbine-specific, but
core-decoupled components, that don't make sense outside of Turbine
(template service e.g.). I would be good to keep them in separate code bases.
I have a few Services, that build standalone vs. Turbine 2.3.x and I
have no intention to roll them into the turbine.jar. I'd like to put
them in their own tree and maintain them there.
Personally, I plan on
turbine/
branches/
2.3/
core/ <- Current TURBINE_2_3_BRANCH
services/
service1/
service2/
service3/
examples/
and I would really like to see
turbine/
trunk/
core/ <-- Current CVS HEAD
components/
turbine-specific-component1/
turbine-specific-component2/
examples/
example1/
example2/
meta/
>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".
+1.
>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/
There is a thread at
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1800768
where I summarized the various projects.
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
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
