[forge-issues] [JBoss JIRA] (FORGE-170) Ensure that plugins can include any dependency
Lincoln Baxter III (JIRA)
jira-events at lists.jboss.org
Tue Nov 20 15:23:23 EST 2012
[ https://issues.jboss.org/browse/FORGE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lincoln Baxter III closed FORGE-170.
------------------------------------
Assignee: Lincoln Baxter III
Resolution: Done
Done and tested.
> Ensure that plugins can include any dependency
> -----------------------------------------------
>
> Key: FORGE-170
> URL: https://issues.jboss.org/browse/FORGE-170
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 1.0.6.Final
> Reporter: Paul Bakker
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Alpha1
>
>
> Due to JBM some dependencies can breae Forge. Most problems have to do with the way Weld currently works. If a class is reimported that is used by the core Weld sees two classes for a injection point. If the cdi api is imported as a compile scoped dependency, this will brake injection in the plugin all together. Forge should scan for these kind of dependencies.
--
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
More information about the forge-issues
mailing list