[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-97) CDI facet should add cdi-api to maven dependencies

Lincoln Baxter III (JIRA) jira-events at lists.jboss.org
Mon Mar 28 22:59:44 EDT 2011

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

Lincoln Baxter III commented on SEAMFORGE-97:

Actually. I'm not sure this should actually take care of adding the dependencies. I think that might better be a role of the "beans" plugin.

Since CDI defines a beans archive as an archive containing beans.xml, it would be potentially harmful to force people to include the CDI api, unless marked as provided scope in the POM.

I might be in agreement with this, but I think we need to make sure that transitive (parent) dependencies are taken into account here. Also, users probably don't want to care which version of the CDI api to include... that could get complicated, but we could always default to the most recent and mark as provided, which should prevent issues. I think that's probably the way to go.

> CDI facet should add cdi-api to maven dependencies 
> ---------------------------------------------------
>                 Key: SEAMFORGE-97
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-97
>             Project: Seam Forge
>          Issue Type: Enhancement
>          Components: Builtin Plugins
>            Reporter: Paul Bakker
> After adding CDI it should be possible to use @Inject etc. in code, but the dependencies are not added to the project. 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the forge-dev mailing list