Fulcrum and Turbine 2.2 ?

[Stephane Bailliez <sb...@imediation.com>]

Hello all,

I would like some info about what is planned for the Turbine 2.2 release.
At the moment I cannot really upgrade to the current CVS code because it
breaks the configuration feature with absolute path for template that was
introduced recently (file:// is no more supported in TurbineVelocityService)
even though it has the new applicationRoot feature.

The code working fine seems to be the one in fulcrum which handles jar,
file:// and applicationRoot.

Is there a plan to backport this in 2.2 to enable the file:// again or will
the Turbine 2.2 code be discarded to move to fulcrum before the release ?

If this is not the case I would be happy to submit a patch for the 2.2 code
since the file:// is critical to ease my development.

Cheers,

Stephane

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Fulcrum and Turbine 2.2 ?

[Jason van Zyl <jv...@apache.org>]

On 11/6/01 4:23 AM, "Stephane Bailliez" <sb...@imediation.com> wrote:

> Hello all,
> 
> I would like some info about what is planned for the Turbine 2.2 release.

Torque will be released first. Which means a documentation and a testbed
have to be finished. Martin and I are working on this now.

Fulcrum will be released first. Again, this involves documentation and a
testbed. This is next on my list of things to start.

Additions will be made to the 2.2 and 3.0 sources so that Torque and Fulcrum
will be pluggable subsystems so that 2.2 users and 3.0 users can take
advantage of the decoupled Torque and Fulcrum. At this point I would like to
declare the Torque and Services code in the 2.1 branch as dead.

At this point all versions of Turbine will be able to use the decoupled
Torque and Fulcrum. Everything will work as expected for people using the
old Torque and Fulcrum but development will stop and people will be strongly
encourage to migrate. A migrator will be provided. For Torque a regeneration
of your OM classes should do the trick but the migrator should take care of
the rest. Moving services over to Fulcrum will definitely require the
migrator.

I use Tambora as my test case because it uses many features of 2.x so I run
the migrator on the tambora source as I work on the migrator to see how
things are going. 

> At the moment I cannot really upgrade to the current CVS code because it
> breaks the configuration feature with absolute path for template that was
> introduced recently (file:// is no more supported in TurbineVelocityService)
> even though it has the new applicationRoot feature.

I don't think this feature was ever in a released version. I removed the
absolute path thing when the applicationRoot feature was added. I wasn't
planning on putting it back. Jon added to Fulcrum and I backported to the
2.x branch for a little while but I don't remember it being in a release?
 
> The code working fine seems to be the one in fulcrum which handles jar,
> file:// and applicationRoot.

I suppose it wouldn't hurt, but I'm not sure if it's worth it. Anything in
Fulcrum is up for change as it hasn't been released and is basically a new
entity even though most of the core service code hasn't changed.
 
> Is there a plan to backport this in 2.2 to enable the file:// again or will
> the Turbine 2.2 code be discarded to move to fulcrum before the release ?
 
> If this is not the case I would be happy to submit a patch for the 2.2 code
> since the file:// is critical to ease my development.

What's wrong with the applicationRoot method? If it isn't we can put it back
in, I don't think it will cause any problems.
 
> Cheers,
> 
> Stephane
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>