[jbosstools-issues] [JBoss JIRA] (JBIDE-13128) CDI Facet not enabled when project depends on javax:javaee-web-api:6.0

Fred Bricon (JIRA) jira-events at lists.jboss.org
Thu Nov 22 09:07:21 EST 2012


    [ https://issues.jboss.org/browse/JBIDE-13128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736402#comment-12736402 ] 

Fred Bricon commented on JBIDE-13128:
-------------------------------------

We decided to check the existence of beans.xml, instead of trying to lookup for specific CDI classes in the project classpath.
So adding cdi jars to the classpath is not even mandatory to enable CDI
                
> CDI Facet not enabled when project depends on javax:javaee-web-api:6.0
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-13128
>                 URL: https://issues.jboss.org/browse/JBIDE-13128
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 4.0.0.CR1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.CR2
>
>
> Testing Adam Bien's [slidegenerator example|http://kenai.com/projects/javaee-patterns/sources/hg/show/hacks/devox2012?rev=458] in JBDS 6, I noticed the CDI  Facet is not applied automatically, yet CDI classes are present in the javax:javaee-web-api:6.0 dependency.
> The CDI configurator basically uses a hardcoded list of known CDI dependencies. It should behave more like the JAX-RS and JSF configurators, where the project classpath is searched for known CDI classes/methods.

--
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 jbosstools-issues mailing list