[
https://issues.jboss.org/browse/CDI-87?page=com.atlassian.jira.plugin.sys...
]
Geoffrey De Smet commented on CDI-87:
-------------------------------------
I don't think general <includes> and <excludes> alone are a good idea.
*They break reuse and transitive reuse:*
If myProject's beans.xml <includes> seam-security's beans.xml then it will
crash,
because seam-security's beans.xml 1.0 depends on seam-international's beans.xml
(but seam-security's beans.xml 1.1 might not).
The point is, myProject doesn't care about seam-international: it uses a certain
version of seam-security and anything that that version of seam-security needs, should be
automatically transitively be included too.
Also, not using <includes> is not on option either, as myProject wants control over
the beans.xml's that get activated (not just everything that happens to be in the
classpath).
Declarative control over classes including in bean archive scanning
-------------------------------------------------------------------
Key: CDI-87
URL:
https://issues.jboss.org/browse/CDI-87
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Packaging and Deployment
Affects Versions: 1.0
Reporter: Pete Muir
Fix For: 1.1 (Proposed)
Weld introduced a XML syntax for this
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira