camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] Reopened: (CAMEL-3659) Upgrade to Spring Web Services 2.0
Date Sun, 13 Feb 2011 12:36:57 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Müller reopened CAMEL-3659:
-------------------------------------


running
{code}
mvn -Pvalidate clean install
{code}
in camel/platforms fails with:
{code}
[INFO]  - step 1: Checking if all artifacts exist
java.lang.Exception: mvn:org.springframework.ws/spring-ws-core/2.0.0.RELEASE is not an OSGi
bundle
        at org.apache.karaf.tooling.features.ValidateFeaturesMojo.validateBundlesAvailable(ValidateFeaturesMojo.java:316)
        at org.apache.karaf.tooling.features.ValidateFeaturesMojo.validate(ValidateFeaturesMojo.java:214)
        at org.apache.karaf.tooling.features.ValidateFeaturesMojo.execute(ValidateFeaturesMojo.java:155)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{code}

We need an OSGIfied version of spring-ws-core. I wonder why the Spring guys didn't release
this as an OSGI bundle...

> 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

       

Mime
View raw message