automate collection and reporting of leiningen download statistics
Pull out the range transformer into its own project to be used in other places with pomegranate. Extend it to also warn for when dependencies are 1) top level and ignored (due to version range) 2) transative and ignored due to a lower version earlier in the chain Currently this does not provide any instruction of how to change the project.clj to remove the warnings.
This eliminates the need to exclude dynapath, since pomegranate and bultitude now use the same version. This also updates core's pom.xml with other recent version updates.
This fixes the issue causing the build failures. The root of it is that dynapath was allowing pomegranate to modify the boot classloader, which caused multiple copies of the same class to be loaded.