You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Marc Hadfield (JIRA)" <ji...@apache.org> on 2016/02/04 15:21:39 UTC
[jira] [Created] (GROOVY-7749) Cannot using maven shading because
of Extension Modules Check
Marc Hadfield created GROOVY-7749:
-------------------------------------
Summary: Cannot using maven shading because of Extension Modules Check
Key: GROOVY-7749
URL: https://issues.apache.org/jira/browse/GROOVY-7749
Project: Groovy
Issue Type: Bug
Components: groovy-runtime
Affects Versions: 2.4.5
Reporter: Marc Hadfield
groovy checks at init time whether there is another groovy on the classpath, and exits with an error if so.
this prevents using maven shading (and similar techniques) to combine multiple versions of jars into a single distribution.
the specific exception thrown comes from here:
https://github.com/apache/groovy/blob/master/src/main/org/codehaus/groovy/runtime/metaclass/MetaClassRegistryImpl.java#L511
this problem occurs often in Hadoop and Spark jobs where multiple versions of Groovy may appear. Specifically in Apache Spark 1.6.0, groovy 2.1.6 is embedded.
A solution would require modifications to how the scans for things like:
"META-INF/services/org.codehaus.groovy.runtime.ExtensionModule" work so that maven shading can merge multiple groovys together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)