[forge-dev] automatic dependency detection too restrictive?
fruehbeck at aon.at
Sun Feb 12 19:04:42 EST 2012
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:
- if I try to package my own org.mvel library via dependency declaration
the module is imported with
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
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.
More information about the forge-dev