RE: [picocontainer-dev] Pico2 releasing it ... before starting work on Composer 1.0

> Can we aim at releasing Pico2 more or less as is?

Before I think one thing we should add back into the Pico and Mutable Pico are
the old function names registerComponentInstance, etc etc etc and have them
marked deprecated (with javadoc pointing to the new method name)

It should help people migrating a great deal.  

> And start Composer 1.0 with the Plexus people at Apache, bringing in
> the remaining features, and reapplying the wisdom from Konstantin's
> branch ?
> 
> Thoughts?

I feel more comfortable doing this with Pico than the additional components
above Nano.  (ie NanoWAR, Deployer, etc)

Perhaps we could do a release and while the container is being hashed out for
Composer, additional work could be done on Nano and the higher level components?
(Rather than tying them into a single big release cycle)

									-Mike





---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email