You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2008/12/03 09:42:05 UTC
[jira] Created: (CAMEL-1139) should we migrate to JUnit 4.x?
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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47838#action_47838 ]
Claus Ibsen commented on CAMEL-1139:
------------------------------------
+1
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48758#action_48758 ]
Charles Moulliard commented on CAMEL-1139:
------------------------------------------
@James
For your information, I have created junit4 tests for the Camel-bindy component based on Camel-2.0. Everything works fine.
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47848#action_47848 ]
Willem Jiang commented on CAMEL-1139:
-------------------------------------
I have a question for the spring 3.0 compatible.
Can camel 2.0 be spring 3.0 and spring 2.x compatible at the same time?
> 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.
[jira] Resolved: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1139.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
2.0.0
> 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
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
>
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48781#action_48781 ]
Claus Ibsen commented on CAMEL-1139:
------------------------------------
No most of camel testing is with 3.8
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48761#action_48761 ]
Charles Moulliard commented on CAMEL-1139:
------------------------------------------
Have you already make a full build + tests of the existing Camel project using Junit4 ?
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47839#action_47839 ]
Claus Ibsen commented on CAMEL-1139:
------------------------------------
Okay more comment. Would be great if Camel 2.0 is spring 3.0 compatible right out of the box.
> 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48759#action_48759 ]
James Strachan commented on CAMEL-1139:
---------------------------------------
Great stuff thanks! :)
> 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.
[jira] Assigned: (CAMEL-1139) should we migrate to JUnit 4.x?
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-1139:
-----------------------------------
Assignee: Willem Jiang
> 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
> Assignee: Willem Jiang
> 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.