[
https://issues.apache.org/activemq/browse/CAMEL-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45807#action_45807
]
Claus Ibsen commented on CAMEL-300:
-----------------------------------
Hadrian we should start considering doing anything with this. If we start
cutting a RC of Camel 1.5 then I guess we should have the OSGi bundles sorted.
> Incorrect maven-bundle-plugin settings cause class duplication in several
> modules
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-300
> URL: https://issues.apache.org/activemq/browse/CAMEL-300
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Victor Salaman
> Assignee: Hadrian Zbarcea
> Fix For: 1.5.0
>
>
> In the camel-spring module the osgi.export property is too greedy. Since the
> maven-bundle-plugin uses ANY resource even if it's a dependency, by
> specifying org.apache.camel.component* actually bundles everything under that
> package from any dependency in the POM, in this case camel-core.
> <properties>
>
> <camel.osgi.export.pkg>org.apache.camel.spring*,org.apache.camel.component*</camel.osgi.export.pkg>
> </properties>
> It should be replaced to something like:
> <properties>
>
> <camel.osgi.export.pkg>org.apache.camel.spring*,org.apache.camel.component.event*,org.apache.camel.component.xslt*,org.apache.camel.component.vali
> dator*</camel.osgi.export.pkg>
> </properties>
> ---
> The camel-stream component suffers from the same symptom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
