[EMAIL PROTECTED] wrote:
I would like to second Danial's request to move Plexus and Summit intoThis is a thing that has been prayed upon by many developers for years... I'm very happy, and I've heard only good things about Turbine from other Avalon committers, that want to be able to use it with what they have as Avalon components.
Turbine CVS. I haven't heard anyone come out and say that Plexus/Summit
shouln't be Turbine 4. So the sooner we move that code into CVS the better,
assuming that it is in some sort of functioning state.
Having said that, I would also like a list of Todo's/Guidelines from Jason
on what aspects are solid and what aspects are subject to change. I think a
lot of developers who are not committers would be willing to help given some
guidelines. I know I have a vested interest in the Turbine platform, and am
willing to help fix my own toolset!
And being tied into the Avalon platform sounds like it would be good for
both communities.
Can I dare?
Avalon + Turbine + Scarab + Forrest/Cocoon, all separate projects like now but integrateable in a complete Java-based solution.
It will take time, but the signs are really good :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
