from time to time there have been talk of an commons-logging-optional
jar to include non-core implementations. i think that the time is now
overdue. i'm going to start by adding the in-memory logging
implementation contributed a while ago and also plan to add some other
stuff such a LogFactory implementation that uses a WeakHashMap to store
the classloaders for use in containers such as JBoss.
in terms of organization, i'm not too sure about the best approach. i
favour the maven-style (a subdirectory under the logging containing one
or more subcomponent directories) but i'd consider other arrangements.
opinions?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
