[
https://issues.apache.org/jira/browse/CAMEL-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959687#comment-13959687
]
Morten Kjetland commented on CAMEL-7074:
----------------------------------------
Our reason for wanting Spring 4 support is to make Camel work with Java 8, as
Spring 3.2.x is not compatible with it.
This can also be fixed if Spring adds java 8 byte-code compatibility in 3.2.9
as described in this issue:
https://jira.spring.io/browse/SPR-11656 (With pull-request)
> Upgrade to spring 4.x
> ---------------------
>
> Key: CAMEL-7074
> URL: https://issues.apache.org/jira/browse/CAMEL-7074
> Project: Camel
> Issue Type: Task
> Components: camel-spring
> Reporter: David J. M. Karlsen
> Assignee: Willem Jiang
> Fix For: 2.14.0
>
>
> Upgrade to spring4.
> There is a non-backwards compatible change in spring 4.x which will cause:
> {noformat}
> java.lang.IncompatibleClassChangeError: Found interface
> org.springframework.test.context.TestContext, but class was expected
> at
> org.apache.camel.test.spring.CamelSpringTestContextLoaderTestExecutionListener.prepareTestInstance(CamelSpringTestContextLoaderTestExecutionListener.java:35)
> at
> org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:326)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:212)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:232)
> at
> org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner.runChild(CamelSpringJUnit4ClassRunner.java:37)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
> at
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:175)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
> {noformat}
> due to https://jira.springsource.org/browse/SPR-7692
--
This message was sent by Atlassian JIRA
(v6.2#6252)
