[forge-dev] automatic dependency detection too restrictive?

Ryan Bradley rbradley at redhat.com
Mon Feb 13 10:53:49 EST 2012

Hi Thomas,

I ran into similar problems with my own plugin development.  Including 
MVEL as a Maven dependency in your pom.xml should resolve this issue.


On 02/12/2012 07:04 PM, Thomas Frühbeck wrote:
> Hi,
> while developing a plugin I found that I cannot access org.mvel classes.
> - if I install my plugin w/o specific dependency declaration I get:
>       java.lang.NoClassDefFoundError: org/mvel2/templates/CompiledTemplate
> - if I try to package my own org.mvel library via dependency declaration
> the module is imported with
> <module xmlns="urn:jboss:module:1.0"
> name="at.tfr.forge.plugin-faces-id-aware.dependencies" slot="...">
> <resources>
> <resource-root path="metawidget-all-2.0.jar"/>
> <resource-root path="mvel2-2.1.RC1.jar"/>
> great so far, but then I get:
> ***ERROR*** [scaffold from-entity] loader constraint violation: loader
> (instance of org/jboss/modules/ModuleClassLoader) previously initiated
> loading for a different type with name
> "org/mvel2/templates/CompiledTemplate"
> So this is a dead end for me. There seems to be no other way to access
> the Mvel libraries than by using maven shade, but this seems to be overkill.
> Could you please rethink the visibility protection strategy or show an
> easy way to use common libraries forge already provides.
> Regards,
> Thomas
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

More information about the forge-dev mailing list