#1 Don't bundle everything in 1 jar

[Tim McCune]

I just spent hours trying to track down why my app
would no longer deploy in JBoss and finally tracked the
culprit down to the adwords-api jar. This jar file has
several non-google classes bundled inside it. The
classes in particular that were causing this problem
were the commons-logging classes. This causes JBoss to
be unable to deploy any app that includes the
adwords-api jar with the error message: "Log4JLogger
does not implement Log". See
http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions
for further discussion of this problem. In addition to
the commons-logging classes, it looks like the
adwords-api jar includes several other classes that
have no business being inside it, like
commons-discovery, axis, etc.

Please either remove these non-google classes from the
adwords-api jar file in your distribution, or at the
very least, provide a google-only jar file alongside
the other, with an explanation of the difference
between the 2.