Paul Hammant wrote:
yep. It's not just the recent issue with altrmi though that concerns me. There is much potential for deadlock with the increasing amount of common code floating around. The problem hasn't really arisen before because commons peeps usually make sure there is virtually no dependency on avalon (well, I actually suspect because excalibur build was broken so long ;)), meaning the dependency worries have basically been restricted to the logging stuff until now.Leo,I think the crucial node is instrument. Can we go ahead with the extra target for that?
nah. When you look at the dependency management on a granular class level, all is well. We just need to set things up so this is reflected in jar packaging.Or should we look at AltRMI a bit closer in that the cornerstone dependancy is optional itself for AltRMI?
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
