ADT.jar bundles useless jars that consequently breaks usage by maven plugins

Steps to reproduce:
1. Try to load the ADT.jar with a maven build plugin
2. See it fail because of funky classloader issues
3. Look at the contents of the ADT.jar file
4. Notice a ton of Maven 2.0.4 jars
5. Notice JFLex (a GPL project)
6. Cry

Actual Results:
A jar file with crap it doesn't need, plus crap that probably can't even legally be in there

Expected Results:
A jar file containing only stuff actually needed for ADT.jar

Workaround (if any):
Gut out the classes that aren't needed.

The OBVIOUS culprit to me is that you are using Smali / Baksmali - which is a maven-built plugin. JFlex - the GPL project that you are including in your non-GPL binary - is used at build time by Smali / Baksmali. It's not used by runtime so Smali / Baksmali is compliant with the GPL and doesn't ship with it.

I would suggest modifying the build to take only the output from maven's TARGET directory for the smali stuff and not whatever the heck it is you are shoving in there at the moment - for both legal and logical reasons.

EDIT: You probably actually were taking the target output before - I apologize for accusing you of not doing that. The issue appears to be that smali was itself including those maven things which were in turn being merged into your ADT.jar jar file.