[X ] Same as above except move Pico to a seperate sub-project so as to remove the Pico deps from the primary J2 tree.
Remember we will need to convert over Fusion, and test and run it before committing these changes
On Jul 22, 2004, at 7:42 AM, Scott T. Weaver wrote:
Scott T. Weaver wrote:
I am getting warm fuzzies in regards to Spring from the responses so far, however I would like to get an offiical vote one moving to Spring Framework as our light-weight container of choice.
The options as I see them:
[ ] Move to Spring Framework as our primary. However, keep Pico in place and testable but don't worry about syncing the assembly script.
[X ] Same as above except move Pico to a seperate sub-project so as to remove the Pico deps from the primary J2 tree.
[ ] Move to Spring Framework and deprecate and eventually remove Pico.
[ ] Stay with Pico.
[ ] Support Spring and Pico fully. (seems really painful)
Regards,
-- ****************************************** * Scott T. Weaver * * <[EMAIL PROTECTED]> * * <http://www.einnovation.com> * * -------------------------------------- * * Apache Jetspeed Enterprise Portal * * Apache Pluto Portlet Container * * * * OpenEditPro, Website Content Mangement * * <http://www.openeditpro.com> * ******************************************
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
