[
https://issues.apache.org/jira/browse/CAMEL-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994108#comment-12994108
]
Christian Müller commented on CAMEL-3659:
-----------------------------------------
Don't worry, I also thought everything at SpringSource is OSGified...
Every time you change something which affects the features file, it's a good
idea to run
{code}
mvm -Pvalidate clean install
{code}
in camel/platforms. This ensures all declared dependencies are valid and all
dependencies could be resolved.
I would prefer to revert the changes in #1070022 and #r1070222 (my change from
today which fixes the wrong dependency to spring-oxm) and upgrade to spring-ws
2.0.1, if it's out. This version should fix the issue we have with the 2.0.0
version.
I would not prefer to build an intermediate OSGIfied version by the ServiceMix
guys.
Christian
> Upgrade to Spring Web Services 2.0
> ----------------------------------
>
> Key: CAMEL-3659
> URL: https://issues.apache.org/jira/browse/CAMEL-3659
> Project: Camel
> Issue Type: Task
> Reporter: Richard Kettelerij
> Assignee: Richard Kettelerij
> Fix For: 2.7.0
>
> Attachments: camel-parent-spring-ws-upgrade.patch
>
>
> Spring Web Services 2.0 is out. It requires Spring 3 as minimum so it fits
> Camel 2.7 nicely.
> The upgrade is very simple, we only need to change the version number in the
> POM of {{camel-parent}}. I've run all unit tests and done some manual testing
> using {{camel-example-spring-ws}} and everything looks ok.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
