On Thu, 2002-07-25 at 12:38, Henning P. Schmiedehausen wrote: > Daniel Rall <[EMAIL PROTECTED]> writes: > > >> You have many services that we don't yet have, and IMHO we could make > >> a common repository for these Components... > > >+1, a common repository would be useful. How about a > >jakarta-avalon-components module in SVN/CVS? > > Hm, > > while the idea is cool, I'd prefer to get the fulcrum stuff to > actually work with T2 and T3 and then migrate a stable code base. The > current fulcrum code base is "preliminary" at best... :-) > > Please allow us to make at least one Fulcrum release before migrating > to yet another platform...
I'm a little confused about the direction of fulcrum right now. My understanding was that Turbine 2.2 is going to be released _without_ it (just decoupled torque, not other services), and we've been talking about Turbine 3 using Avalon for its component needs. Thus, my expectation was that fulcrum would be disolved, and the services there that need to / should be retained would be converted to components for Turbine 3. Am I off base here? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
