commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <aj...@trysybase.com>
Subject Re: [logging][PROPOSAL] a solution to incompatibility between log4j versions
Date Wed, 19 May 2004 22:50:21 GMT
> Version numbers
> Together with deprecations this makes it easy (well sort of) to see
> which piece of software that is a drop-in replacement and which will
> require changes to your own code. In my book upgrading from 1.0.1 to
> 1.0.2 should be a walk in the park, but upgrading from 1.0 to 2.0
> propably means I have to work late. If log4j decides to drop the
> Category class (which is their decision to make) I feel that would make
> it log4j 2.0 rather than 1.3. If commons-logging were to drop support
> for log4j 1.1 I think that would have to be commons-logging 1.1 rather
> than 1.0.4.

Good points, and interface class removal, after deprecation, is covered in
that document.

> Isn't there a document about this somewhere at Apache?

Good point. It moved, but I found this via Google:

    http://jakarta.apache.org/commons/releases/versioning.html

Not sure if folks outside of Jakarta Commons are held to this standard. :(

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message