[Proxool-developer] Why embeed external packages?

[Claudio D. <o1...@ti...>]

These days I was thinkering with an annoying _bug_: while my classes logs - 
using external JCL/SimpleLog - to a text file, proxool-0.8.3 logs - using its 
internal JCL/Jdk14Logger - to System.out.

I think the problem is in the re-writing of "org.apache.commons.logging.Log" 
property in "org.logicalcobwebs.logging.Log" (internal JCL does not act the 
same way as external one).

So, I understand version problems, but why not simply retain external package 
original names instead of embeed them into org.logicalcobwebs super-package? 
I understand this for one or few more classes (see util.FastArrayList, I did 
the same with a *modified* version of catalina.util.FastDateFormat).

This gives users the ability to un-embeed external packages (avoiding useless 
duplication of code), and saves you from version problems (even if I think 
this is not a real problem expecially for packages like Concurrent and 
Logging).

In any case you can distribute all sources needed by Proxool (see Apache 
XmlRpc which boundles uk.co.wilson.xml.MinML and uk.org.xml.* in its source 
distribution). I mean:

proxool-x.x.x-src.jar
    |
    +-- org/logicalcobwebs/proxool/*.java
    |
    +-- org/apache/commons/logging/*.java
    |
    +-- EDU/oswego/cl/dl/util/concurrent/*.java
    |
    +-- net/sf/cglib/*.java
    |
    +-- ...

...Just an opinion.

Claudio Destro <cd...@tn...>