On Apr 7, 2010, at 10:36 PM, Gary Gregory wrote: > Clearly, since Chainsaw V2 is the current version, it seems odd to deliver > the code for Chainsaw V1. This should be deprecated in a point release, 1.3 > or 2.0, not in a 1.2.x maintenance release though.
You could never say with certainty that there is some app out there that depended on same fragment of Chainsaw or LF5 code to be present. The Eclipse statement of compatibility phrases this as "API Usage Assumption: Every aspect of the API matters to some Client." I agree we can't yank anything out of log4j.jar in a 1.2.x release. However, I don't think that anything would prevent us from offering an alternative lighter jar (or jars) as part of a 1.2.x release. The easiest would be to strip out Chainsaw 1 and LF5 out from the jar, maybe log4j-no-gui.jar? I've logged https://issues.apache.org/bugzilla/show_bug.cgi?id=49077 and https://issues.apache.org/jira/browse/LOG4J2-34 for an no gui alternative jar for log4j 1.2 and modular design for log4j 2 respectively. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
