[
https://issues.apache.org/jira/browse/CAMEL-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6337.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
2.13.0
Assignee: Claus Ibsen
Thanks for the patch.
> camel-cdi dependencies are wrong for most cases
> -----------------------------------------------
>
> Key: CAMEL-6337
> URL: https://issues.apache.org/jira/browse/CAMEL-6337
> Project: Camel
> Issue Type: Improvement
> Components: camel-cdi
> Affects Versions: 2.11.0
> Reporter: Romain Manni-Bucau
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.13.0
>
> Attachments: camel-6447.patch
>
>
> Hi,
> because of its main camel-cdi import:
> <exclusions> <!-- provided by the container -->
> <exclusion>
> <groupId>org.apache.geronimo.specs</groupId>
> <artifactId>geronimo-atinject_1.0_spec</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.geronimo.specs</groupId>
> <artifactId>geronimo-jcdi_1.0_spec</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.geronimo.specs</groupId>
> <artifactId>geronimo-interceptor_1.1_spec</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-impl</artifactId>
> </exclusion>
> </exclusions
> It is wrong since all containers (embedded or not) will provide it. The only
> case where it is relevant is the main and IMO it is better to use scope
> provided and ask for inclusion when needed (main). The main case shouldn't
> drive any dependency.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
