1) Use class dependency analyzer. Check for classes loaded via reflections too!!! class dependency analyzer was also used to strip third party libraries from unused classes

2) Move runtime classes to clover-runtime module.

3) Rename packages to com.atlassian.clover.runtime.* but keep few core classes in com_atlassian_clover. Reason: Clover-for-Ant will still have single clover.jar probably and it will use FileInputStream(clover.jar) to dynamically extract classes form archive so we must be able to distinguish them. cancelled; too many changes in referenced classes and runtime still "borrows" few classes from core

4) Enhance build script to publish this as com.atlassian.clover:clover-runtime artefact on Atlassian Central and Maven Central.

Note:

• for backward compatibility clover-core shall still contain runtime classes and it's name will not change (com.atlassian.clover:clover)
• we can add dependency to clover-runtime in pom.xml, however - just to keep programmers informed about this change dependency not added as clover-core already bundles the clover-runtime

5) Update documentation on CAC and inform that new, small artifact is available since version 4.0.x. done

6) Update UML in clover-maven-module-structure.graphml done

7) Test it with Clover-for-Android (original clover-core exceeds method limit in Dalvik image) couldn't test as Android Studio uses Gradle now and is based on IDEA not Eclipse