Use java code parsing to determine if jars are required

[xiwenc]

High level:

• Walk through all java files in the project

• Create list of classes with full names. E.g. org.json.blaat.hello

• Walk through all jars and create list of all classes with full names also

Compute the difference and identify which jars can be removed.

[zeeshantariqrafique]

Looks good , I would like to pick this up if it is already not taken ?

[xiwenc]

Hi Zeeshan, feel free to implement this. Didnt get around to do this yet.

[xiwenc]

There is one catch (challenge): how to deal with transitive dependencies. Not all jars will have a direct dependency from a java file. How do we know a jar depends on another jar?

[zeeshantariqrafique]

There is one catch (challenge): how to deal with transitive dependencies. Not all jars will have a direct dependency from a java file. How do we know a jar depends on another jar?

Hi Xiwen, That is a good point you make Maven or extract byte code (.class) from jar and check for class duplicity comes to mind.

[xiwenc]

Yes that's a great idea. Reverse generate a mvn pom.xml.