[jira] [Commented] (CAMEL-13491) CamelTestSupport.isCreateCamelContextPerClass no longer works for junit4 tests

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838029#comment-16838029 ] 

Claus Ibsen commented on CAMEL-13491:
-------------------------------------

You are welcome to work on a fix and submit a PR

> CamelTestSupport.isCreateCamelContextPerClass no longer works for junit4 tests
> ------------------------------------------------------------------------------
>
>                 Key: CAMEL-13491
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13491
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-test
>    Affects Versions: 2.23.0
>            Reporter: Jan Hallonsten
>            Priority: Major
>
> With the changes in 
> org.apache.camel.test.junit4.CamelTestSupport done during the work on https://issues.apache.org/jira/browse/CAMEL-12534 the camel context is now recreated for every test regardless of the return value from
> isCreateCamelContextPerClass()
> . Since junit4 creates a new instance of the class for every test the variable tests will be recreated and initialized to 0 for every test.
> This condition in tearDown will always be true
> {code:java}
> // code placeholder
> if (tests.compareAndSet(v, v - 1)) {
>     if (v == 1) {
> {code}
> which stops the camel context after every test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)