It would be nice to keep an example of how to assemble J2 in another
container. However, we would not want to invest to much time in keeping
it up to date in terms of assembly.
Roger Ruttimann wrote:
What's the benefits of keeping Pico around and not moving to Spring
completely?
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.
[ ] Same as above except move Pico to a seperate sub-project so as
to remove the Pico deps from the primary J2 tree.
[ X ] Move to Spring Framework and deprecate and eventually remove
Pico.
[ ] Stay with Pico.
[ ] Support Spring and Pico fully. (seems really painful)
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
******************************************
* 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]
