[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-377:
-----------------------------------
I think there are actually 2 parts in the game which are both kind of broken:
a.) CDI should not pickup any @Inject from anywhere. This breaks all kind of projects
which use other JSR-330 containers like Spring, guice, etc.
b.) maven-3.1 now exposes internal plugins via JSR-330 annotations (and the atinject API
as well). That will not only break CDI containers but actually _all_ other projects which
contain any JSR-330 code as well. We should have remained with our highly proprietary
plexus injection container. Discussing over in Maven how to deal with it.
automatic JSR-330 annotation processing problematic
---------------------------------------------------
Key: CDI-377
URL:
https://issues.jboss.org/browse/CDI-377
Project: CDI Specification Issues
Issue Type: Bug
Components: Java EE integration
Affects Versions: 1.1.PFD
Environment: glassfish-4
Reporter: Reuben Pasquini
Labels: CDI, guava, guice
Fix For: 1.1.PFD
The jsr-330 dependency injection annotations (javax.inject.*) find use in javase
environments using IOC packages like guice.
Adding a dependency on a jar that uses guice or whatever in a javase environment
to a war deployed to a jee7 container
results in CDI processing annotated classes intended for
app-managed injection. See this ticket filed with guava for a concrete example:
https://code.google.com/p/guava-libraries/issues/detail?id=1433
--
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