My problem is simple, I do not want to have to distribute commons-logging for because attributes depends on it. I do not want to distribute it becuase it will never get called. It is a compilation dependency only.Can we consider one of two solutions for this _single_ use of commons logging
1) Removal of the commons-logging from attributes?
2) Backwards compatible rework that will allow the application to run
without commons logging in the classpath (or classloader tree for
complex deployments).
I undersatnd this single use is not pragmatic, do you have problems with classloading in logging ? I have promissed to fix class loading in this component, it depends on ThreadContext classloader and it was a problem with this strategy in phoenix a year ago. logging works on phoenix at this time, does not it ?
- Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
