Peter Courcoux wrote:
My view and Eric's if I recall correctly was that turbine should
ideally have service managers for Avalon, Spring, Hivemind, osgi etc,
which would allow turbine users to take advantage of components from
any of these sources, preferably wrapping all of these in some common
lookup service which searched all the framework service managers for
the required component.
Rather than 2.4 I think this could be a goal for turbine 2.6 - perhaps
we should cal it turbine 4 (skipping 3 due to its historical baggage).
Clearly, the best bet is to have an Avalon Service Manager working, as
this is the easiest way to maintain backwards compatibility. The
others can be added as required.
Is there a document somewhere which explains the steps needed to
replace ECM with YAAFI in a t2.4 application? I'm pleased to hear that
you are successfully using YAAFI and I ought to try it out.
If we want to get 2.4 out the door in a reasonable timeframe we need to
make some decisions and lay out some plans. From what I can see the
most important issues/steps to get us to 2.4 are:
1. Determine the service manager(s) that we will offer for 2.4 -
compatibility is an excellent reason for sticking with an Avalon based
implementation for this release and lack of available resources is a
great justification for not opening the gates to all the other options
(sure, lets do it, but not in this cycle).
2. Porting remaining 2_3 branch fixes and enhancements over to the trunk
and fulcrum. This includes intake, parser, template and security. The
joy of fulcrum will be that these and the other fulcrum components can
be released individually from one another. Since code is available we
should also provide for the AJAX support.
3. Generally making sure everything works (testing, bug fixes,
documentation, etc.)
Jürgen is clearly interested in moving jumping in with maven 2 support,
JMX support, etc. These, along with the support of multiple service
managers are great, but I think they would be best addressed as the next
steps on from a 2.4 release.
I propose we work on items 1 and 2 above with a view to producing beta
releases of 2.4 and the as yet unreleased fulcrum components. Once we
have these we can truly encourage the adventurous to adopt 2.4 and work
on polishing things up for a final release.
Comments on the above and volunteers to work on outstanding issues are
most welcome.
I intend nominating Jürgen and Thomas as committers in the near future
(after following due process) so as to beef up the active committership.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
