Stephen Haberman wrote:
Hi,Is anyone using Fulcrum HEAD? I can tell the Avalonization has/was started, what with FulcrumContainer and what not, but is anyone using it in an Avalon environment (or non-Avalon)? Or is it in a suspended state?
Yes, I have been working with it - but it is quite messy at the moment.
Basically I'm wondering if I could investigate refactoring things a bit to be more elegant. E.g. get rid of the old singleton TurbineXxx classes that just had wrapper methods around the class, move stuff over to the Avalon lifecycles/configuration, and then get rid of the rest of the cruft.
Let the refactoring begin!!!
I don't think it would be too hard to do all this. Two thoughts though:(Also note that my time frame for doing the refactoring is not within the next few days, but over the next few weeks.)
1. Avalon fulcrum support needs to be integrated into the Turbine-3 tree. John McNally: you made the changes to avalonize fulcrum. Did you have changes to check into the T3 tree also? I filed a bug and posted a patch, but I don't know if its what people had in mind.
2. With the advent of maven, would it make sense to split fulcrum into component builds like maven has in its tree? This provides an area for documentation of each component. Then if I want to use just intake or just the factory service I can. Granted, this is getting pretty fine grained. Thoughts?
- Dan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
