Mark Womack wrote:
So, I don't remember if anything specific has already been applied to
1.3 for the deadlock issue (Elias can speak to that better probably).
However, it is an issue that will be addressed in 1.3 in the near
future. We've been very reluctant to make any of these kinds of
changes in 1.2 due to the unknown impact for a "mature" release.
After I really dug into the 1.3 sources I certainly got the impression
that this effort had at least begun, but I may be utterly mistaken.
It looks like you have been working on some patches for the
compatibility issues. We'll take a look at them and get moving on
this. As I said earlier, I'd like to have you involved in the
process, and appreciate your effort and input. As committers, it is
up to us to facilitate and apply this kind of stuff to the code if we
agree it is a good idea. I'm pretty sure we all agree that binary
compatibility is a "good idea". :-)
Thanks. I've filed bugs for the more troubling issues -- compatibility
and otherwise (e.g. the listener interfaces with methods that are never
called bothered me too) and provided suggested patches except in one
case where further discussion as to direction appeared necessary (and in
this case the code changes are really simply and obvious).
I didn't file a bug or provide patches to the LoggerRepositorySelector
interface expansion issue as this compatibility issue may be acceptable
if few enough folk implement this interface -- else I think we need to
leave LoggerRepositorySelector as it was in 1.2 and create a
sub-interface to introduce the new methods. [It is quite possible to
implement all of the methods and yet build against 1.2 and run against
1.3, and this is a "high-end" usage, so all-in-all I can see leaving
this as it is in 1.3 if everyone else can.]
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
