[
https://issues.apache.org/jira/browse/CAMEL-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368888#comment-14368888
]
Raúl Kripalani commented on CAMEL-8514:
---------------------------------------
Hello,
This data format should have been depending on Castor 1.3.2, not on the SMX
bundle for Castor 1.3.2. You are right.
However, the problem is that vanilla Castor is not OSGi-ready. Upgrading to
Castor 1.3.3 without a corresponding OSGi-bundle from the SMX community
effectively creates a version fork.
The problem is that the camel-castor unit tests would run against vanilla
Castor 1.3.3 whereas OSGi users would be using a lower version. This leaves the
community in a brittle position, as it makes it relatively easy to introduce
new features that are not backward compatible without anyone realising –
because no test would report it.
Therefore I can see two solutions:
* Contribute an upgraded OSGi bundle to the SMX community (quite a simple task)
– but then we have to wait for their next bundles release so we can use it.
* Create 2 JUnit executions for this component: one against the OSGi bundle,
one against the latest vanilla Castor library.
Ideas?
Regards,
Raúl.
> 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)
