Size of common jar file

[David Van Couvering]

I'd like to understand the issues and concerns of the size of a common 
jar file.  Further inspection has shown that pulling in Monitor results 
in a large subset of the iapi and impl packages being pulled into the 
common area.  This will result in a larger footprint for the client.  Is 
this a showstopper?  I'd like to know before I spend too much time 
refactoring.

And no, I haven't forgotten about the independent versions of client and 
embedded drivers issue :)  I'm doing some prototyping which has brought 
up this question for me.

Thanks,

David