Leo Simons wrote:
Correction - I'm not implying that "lifecycle extensions are part of the framework" - if fact I've said the opposite.
uh, okay then!
lifecycle extensions are but one way of several setups currently in use for accomplishing a certain goal. So the lifecycle stuff is not a "standard extension" of avalon-framework, just "an extension".
I agree.
cool :D
So, what is the point you are raising?
that it makes no sense to put this stuff into the avalon cvs module instead of into the excalibur cvs module /at this point in time/ because it would be work that would unneedlessly delay releases and result in confusion, integration build failures, and other nasty stuff. IOW: "you should not be worrying about cvs structure so much" :D
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
