camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge0ffrey <>
Subject [GitHub] camel pull request: Fix test corruption by6 3 upgrade + ignore tes...
Date Tue, 13 Oct 2015 12:45:31 GMT
GitHub user ge0ffrey opened a pull request:

    Fix test corruption by6 3 upgrade + ignore test due to upstream issue

    The master code currently suffers from PLANNER-468 and a corrupted test case.
    This PR fixes the test case. It also ignores the test case temporary, because PLANNER-468
makes it fail. It clearly comments when it can and should be unignored.
    This PR is better than the current master state. An additional improvement(?) could be
to revert optaplanner from 6.3 to 6.2 to fix the deamon mode until optaplanner 6.3.1+ is out,
but I am not sure if that's desired as it would impact the drools & jbpm version too.

You can merge this pull request into a Git repository by running:

    $ git pull fixTestCorruptionBy6_3Upgrade

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #636
commit 697e735966014d292ff84633598e9e6ffd604d62
Author: Geoffrey De Smet <>
Date:   2015-10-13T09:11:11Z

    camel-optaplanner test: extract local variable mockEndpoint + extract inner class RemoveComputerChange

commit 5e1067e3df9d6538959994937037e64430ee82ad
Author: Geoffrey De Smet <>
Date:   2015-10-13T12:16:38Z

    camel-optaplanner: fix slf4j warning because there are 2 bindings in the classpath

commit bd1c3957d339ec5a917a482faca94e820465412e
Author: Geoffrey De Smet <>
Date:   2015-10-13T12:37:07Z

    camel-optaplanner: Ignore test testAsynchronousProblemSolving until PLANNER-468 is fixed


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message