[picocontainer-dev] Moving towards a Nano 2.x release

Hi all,

now that Pico 2.2 is out, I feel we should take off the foot from the 
Pico pedal for a second and focus on Nano 2.x.

I've verified that all Nano unit tests pass with latest Pico release.
But perhaps moving from 1.x to 2.x is a good opportunity to drop some 
old baggage - given that it's now 5 years since some of the modules were 
written or conceived.

Eg, I've dropped hibernate2 support from persistence, since Pico and 
Nano 2.x mandate JDK 1.5, I can't think of any reason why someone would 
still be on hibernate2 - if they do want to use of course, the 1.x 
versions still support it.

A similar argument applies to some other libraries.  Eg:

- do we want to continue support for struts1 and webwork* now that t 
they've merged into struts2?
- does it makes sense to support nanoweb which was at best a proof of 
concept?  there are a number of web frameworks out there which support 
dependency injection.

A more general note regards the use of the namespace nanocontainer. 
Would it make sense to drop it in favour of pico extensions, eg:
- nanocontainer -> picocontainer-script
- nanowar -> picocontainer-web
- nanopersistence -> picocontainer-persistence

Note that these would still continue to have their subgroup of module 
and independent release lifecycle.  It's simply a question of whether 
the namespace picocontainer (as more recognised and understood) was 
better than nanocontainer.

Finally, I've checked in test case that proves how Paul's Storing 
behaviour can be used to replace the DefaultContainerRecorder (the test 
case is identical in scope to DefaultContainerRecorderTestCase)

https://svn.codehaus.org/picocontainer/java/2.x/trunk/nano/container/src/test/org/nanocontainer/reflection/StoringContainerTestCase.java

Konstantin, since you originally wrote the recorder with Aslak, want to 
take a look and see if these satisfies any other use case you may have?

Looking forward to your comments on the above.

Cheers




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

    http://xircles.codehaus.org/manage_email