my apologize, if i don't understad your suggestion
but with groovy/gradle we must use (only e.g.)
for avoid conflict with asm3 and asm >= 4
maven signature has no effects for gradle problems (at build/run
you want to create a new package e.g. objectweb-asm3-shaded ?
Well groovyjarjarasm.asm.ClassWriter is in groovy-all.jar. It is a
jar which bundles all its dependencies and among them shaded asm3.
AFAIK, we don't build this jar in Fedora. But for rest of the groovy
jars you can replace all "org.objectweb.asm" strings in groovy 1.8.9
sources with "org.objectweb.distroshaded.asm" and instead of
"build-jar-repository objectweb-asm3/asm-tree" use
"build-jar-repository objectweb-asm3/asm-tree-distroshaded". groovy
uses asm3 internally, so then you can put groovy jars together with
their dependencies (distroshaded asm3) on classpath of some other
project (which requires asm4) and there won't be any asm3/asm4
conflicts. At least not caused by groovy.
java-devel mailing list