[
https://issues.apache.org/jira/browse/CAMEL-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368955#comment-14368955
]
Thomas Diesler commented on CAMEL-8514:
---------------------------------------
Yes, I noticed that. However, OSGi is one of potentially many clients. OSGi
itself is a declining technology, which will become even more marginalised when
JDK modularity enters the scene.
The non-existence of a castor-1.3.3 bundle should IMHO not prevent Camel to
move forward and upgrade the castor library. The OSGi community may want to
provide a castor-1.3.3 bundle, which Camel can then integrate in its Karaf
feature definition. There may however never be a call for a castor-1.3.3 bundle.
For the WildFly Camel integration, it would AFAICS also work to stick with
castor-1.3.2 and only fix the dependency from camel-castor to (non-osgi)
castor-xml
> Update to castor-1.3.3
> ----------------------
>
> Key: CAMEL-8514
> URL: https://issues.apache.org/jira/browse/CAMEL-8514
> Project: Camel
> Issue Type: Improvement
> Reporter: Thomas Diesler
> Fix For: 2.15.1
>
>
> The camel-castor component should depend on plain castor-xml instead of an
> aggregate bundle from servicemix
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
