[
https://issues.jboss.org/browse/FORGE-170?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III updated FORGE-170:
-------------------------------------
Summary: Ensure that plugins can include any dependency (was: Scan plugins
for potential problematic dependencies)
Fix Version/s: 2.0.0.Alpha1
Affects Version/s: 1.0.6.Final
Description: 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. (was: Due to JBM some dependencies can brake 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.)
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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira