Hey Jake,
The current system has the advantage of building a functional log4j.jar out of the box. It is in place since about 1659 and in practice no one has ever complained about it.
At 07:19 PM 12/17/2004, you wrote:
Hi Scott,
I think that your change is, indeed, consistent with the rest of the build. However, I think the entire logic of this is flawed. It allows for the generation of an incomplete log4j.jar (as you mentioned) and that just shouldn't be allowed. If there are compile-time dependencies, they should be mandatory. At runtime, if one doesn't use some of the features that require extra dependencies, then they are optional. But the build should never allow them to be optional. All or none.
Jake
-- Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
