manifest updates - dependencies - cornerstone - excalibur

I've started going though the manifest entries in some of the Excalibur 
packages - thread, threadcontext, pool, collections, etc. with the 
objective of getting these into more well structured state so that 
packaging cornerstone units can be done with more integrity.

I've started off with the creation of a seperate 
cornerstone-threads-1.0.jar in Cornerstone with the following dependencies:

   cornerstone-threads-1.0.jar

     --> avalon-framework-4.1.2
     --> excalibur-thread-1.0 (HEAD)

   excalibur-thread-1.0 (HEAD)

     --> excalibur-threadcontext.1.0 (no dependencies)
     --> excalibur-pool:1.1

   excalibur-pool:1.1

     --> avalon-framework-4.1.2
     --> excalibur-collections:1.0 // <---- replaced by commons 
collections ?

An immediate question I has is if the excalibur-pool package should be 
updated to build against commons collections package (involving updates 
of the build file and pool manifest)?  Secondly, I think we should up 
the version of excalibur-thread from 1.0 to 1.1.

Any thoughts?

Cheers, Steve.

   


-- 

Stephen J. McConnell
mailto:[email protected]
http://www.osm.net