Ok, this changes my opinion a bit.
I was under the impression that moving (almost) all services from Turbine to
the Fulcrum projects was a goal, but I agree with what you say that it only
makes sense if the components are to be used outside Turbine.
I will think about this a bit and see how easy/hard it is to move code to
Fulcrum. Another advantage of having the services in Fulcrum is of course
that they can be released easily.
I'll come back to this later.
/Ludwig
-----Ursprungligt meddelande-----
From: Thomas Vandahl
Sent: Saturday, October 15, 2011 7:58 PM
To: Turbine Developers List
Subject: Re: [Discuss] fulcrum-template
Hello Ludwig,
Am 11.10.2011 17:31, schrieb Ludwig Magnusson:
1 Should bugs be resolved in core or in fulcrum-template?
Difficult to decide. fulcrum-template has not been maintained for a long
time. On the other hand, the template bugs are obviously not in Turbine
2.3.3 which means that I missed the modifications when I attempted a
merge. Fixing the bugs would be a simple port of the 2.3.3 version.
I say in fulcrum-template since this is where we are heading anyway.
I always thought that Fulcrum components make sense when there is at
least the remote possibility to use them outside of Turbine. I don't see
that for the TemplateService (as well as for the PullService, too). But
I'm fine with either decision of yours.
2 Should fulcrum template not be like security, i.e. one api-project with
TemplateEngineSercive etc. and one for each template type.
If we keep the current structure, both the velocity and jsp libraries
needs to be complete before we can release any of them.
That would be a real achievement. However, keep in mind that one might
want to use different template services at the same time. Our default
Avalon container YAAFI doesn't support that.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org
For additional commands, e-mail: dev-h...@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org
For additional commands, e-mail: dev-h...@turbine.apache.org
