[Proxool-developer] Logging class refactoring?

[Martin C. <mus...@us...>]

All.

So I've been porting documentation over and reading it as I go...

Question:

I understand that we wanted to remove the dependency of the 
commons-logging package. Mainly I guess because JDBC drivers standardly 
are one package. Additionally, because it would be good to keep the 
dependencies down.

I guess the question is why refactor over redistribute? To make a single 
JAR the Ant script could unjar the commons-logging JAR and then jar it 
back in the Proxool JAR.

True, we could potentially run into version issues in the future. Our 
trade off as I see it though is that we loose the reusability using 
existing implementations of Log (without refactoring them too). Plus we 
have a bit of a maintenance head ache on our hands.

I am sure there are some good arguements to refactor over redistribute? 
I'd be interested in hearing these arguments. Mainly because I've been 
considering this issue often in other projects and usually just rebunlde 
the JARs.

Cheers.
Martin