Leo Sutic wrote:
No need to change package names - just some fine-grain selective reasoning in the build file.
From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
Peter Donald wrote:
On Tue, 11 Feb 2003 16:06, Berin Loritsch wrote:PLEASE, find
I have improved the framework build some, so that the announcements are built again. The changes are also back in. I want to provide ample time for anyone to bring up issues with the build.
interfaces yet.any and all issues and bring them up now--no matter how minor.I don't recall whether we have separated out impl and
At barexalan/xerces/logkit/log4j/etc classes
minimum we have to be able to have all
in separate jarsI agree.
The current packaging complicates life if you trying to construct clean classloader hierachies (you end up duplicating the framework jar on both internal and external loaders because the framework classes have implementation dependencies - e.g. use of AvalonFormatter requires LogKit in the classloader hierachy at or above AvalonFormatter which means that you canot share the framework jar).
How do others feel about getting this in place now? If we are going to do it we kind of need to to do ASAP otherwise we should put it down as an action item for the subseequent release.
Cheers, Steve.
If this means no changes to package names, and that we'll have avalon-framework.jar avalon-framework-impl.jar then I'm fine with that.
Cheers, Steve.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
