commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Tagunov <>
Subject Re[2]: Logging packaging questions
Date Tue, 01 Jul 2003 08:08:44 GMT
Hello Nicolas!

AT> Now, did I get it right that _despite_ jakarta-logging will be shipped
AT> as a single jar all your stuff _will_ work okay since jakarta-logging
AT> will detect what is available on the classpath and what is not?

NM> Basically if/when we had split the backends we'd had provided a backends
NM> symlinks pointing either to log4j, jvm or build-in (with automated
NM> priorities). This symlink would have been added to all the logging users
NM> classpaths/jer directories
NM> So we would have insured there was always a backend on the system,
NM> without duplicating classes.

NM> The current solution will be the death of log4j since no one will take
NM> the pain to put it manually in the classpath (as it would have, if the
NM> split had proceeded)

I'm sorry, Nicolas, I do not get you.
What is the difference between putting
into the classpath that automatically pulls in log4j.jar
and putting there
jar directly?

What has changed? Why one is more difficult for users of your
framework then the other?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message