It's just that nobody had time to look into it.
And it might well turn out that the effort of removing the dependency on commons logging is too much for the benefit we'd get. So far I had the impression that nobody wants to bother with logging discussions and I really share that view, so let this thread just die if all are happy with the current situation.
I don't see any integration problems without commons logging as virtually everybody is using Log4j. Another solution would be a simple Delegate (implemented dynamically typed) in Hibernate and a configuration option. In the end we could remove one JAR dependency on almost all installations of Hibernate I guess.
------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
