Hi folks,

I started to make an experimental branch

+) I released Fulcrum 3.0.0 to have a baseline for tackling Turbine
+) I tagged the CVS HEAD with "TURBINE_2_4_M2_BRANCH"

On this branch

+) I havn't committed anything yet
+) I updated the project.xml to use the released Fulcrum components
+) removed ECM libraries and integrated YAAFI
+) updated the TurbineAvalonComponentService and AvalonComponentService
+) got all JUNIT tests running using the YAAFI container
+) I uploaded the current site to http://people.apache.org/~sgoeschl/turbine-2.4-m2/



Cheers,

Siegfried Goeschl

-------- Original Message --------
Subject: Current State of Turbine 2.4.1?!
Date: Thu, 12 May 2005 18:23:15 +0200
From: Siegfried Goeschl <[EMAIL PROTECTED]>
Reply-To: Turbine Developers List <[email protected]>, [EMAIL PROTECTED]
Organization: IT20one GmbH
To: Turbine Developers List <[email protected]>




Hi folks,

today I started to migrate my old Turbine application running on Torque 3.0 and Turbine 2.2. to more actual versions ... :-) ... the big question is to move to Turbine 2.4.1 M2?

Being adventurous I got the CVS HEAD from the CVS repo ....

1) the build is broken since torque-20041102.134240.jar is nowhere found

2) can someone shed some light on the following statement in the project.xml regarding the broken Torque dependency "needed for integrated email, will be replaced by commons-email"?!

3) is it feasable to call a vote for removing ECM and Merlin to be replaced with YAAFI? I'm dead serious - Turbine 2.4.1 is a dependency graveyard - I counted 74 JARs needed for the compile whereas 30 of those JARs belong to ECM and Merlin.

4) I suggest an incremental phase-out of Turbine services already found at Fulcrum otherwise I'm without any chance to get a M2 running. But I'm puzzled - a few of Fulcrum services are already included but there is still the Turbine version around? Is this intentional or an oversight?

Cheers,

Siegfried Goeschl



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Reply via email to