Danny Angus wrote:
My only concern
is that there is an overlap between jars used as part of the Phoenix
distribution that are also used or implied by the James distribution.
This is also my biggest gripe. I don't really think conscience would allow me to sancion a release of James which was dependant on two different versions of the same Avalon sourced class. It seems like a receipe (is that how you spell that?)
recipe
:-)
for disaster.
My understanding is that your releasing 2.1.2 from a specific CVS branch which has not been synchronized with the CM-SM migrated HEAD. The 2.1.2 branch presumably is using the Phoenix release and the old corenerstone.jar file. Is that assumption correct? I also share your concerns about releasing collocated jars of different versions (but my impression is that this is not being proposed for the James 2.1.2 release).
As far as the subject of dealing with multiple versions of particular Avalon release - this is something I've been paying rather a lot of attention to. For example, under the Merlin container it is a requirement that you declare the dependencies that your have for your application - more specifically - you should not be linking your runtime James build to the particular version of a jar file that a container uses - and the container should not force you one way or another in this regard. I'm not that familiar with the classloading arrangements in Phoenix but I do not that more effort will be going into this area in Merlin to ensure that there is a complete isolation between jar files used by Merlin and jar files used by clients.
It's a recipe for independence.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
