[ https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy... ] Reuben Pasquini commented on CDI-377: ------------------------------------- @Mark - Maven 3.1 may be ok with @Inject annotations - for example - guice is lazy in its annotation processing, so guice will only inject a mavin class if it's required by some class needed at runtime: class Plugin { ... @Inject() public Plugin( MavinThing thing, ... ) { ... } ... } In other words - mavin's IOC world can exist along side some plugin's IOC world assuming the two worlds are working with their own set of classes. I guess OSGi is designed for this kind of plugin dso hell ... I think CDI is causing problems, because it eagerly allocates @Singleton classes that may not be needed at runtime, and may not have all dependencies available either. There are several ways CDI could make itself a more friendly JSR330 neighbor. It would be great if either or both of: o. CDI ignored jars that do not include a beans.xml o. CDI provided some outside-the-jar override mechanism in a .war or .ear or whatever file like WEB-INF/web.xml or the app-root META-INF/beans.xml: <cdi-config><exclude-jar>guava.jar</...></cdi-config> Something like that ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira