[
https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47853#action_47853
]
James Strachan commented on CAMEL-1139:
---------------------------------------
AFAIK 3.0 is backwards compatible - its just they are deprecating some stuff
(like JUnit 3.x support). The only other change that might impact us is the
JavaConfig becomes part of the standard framework (but since its modular its no
biggie) - so we might change the JavaConfig groupId/artifactId. Also it looks
like Jersey is gonna be integrated; so we can simplify the camel-rest module
too. But the vast majority of Camel should work on 2.x too
We might want to create an integration test on 2.x to check things still work
OK?
> should we migrate to JUnit 4.x?
> --------------------------------
>
> Key: CAMEL-1139
> URL: https://issues.apache.org/activemq/browse/CAMEL-1139
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Fix For: Future
>
>
> 3.x is gonna be deprecated in Spring 3.0 - so maybe we should migrate our
> test cases from JUnit 3.x to JUnit 4.x?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
