camel-git

Clone Tools
  • last updated 23 mins ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
CAMEL-11002 - Camel-Blueprint, prevent JMX re-registration in case of failed Context

CAMEL-11002 - Camel-Blueprint, prevent JMX re-registration in case of failed Context

CAMEL-10987: Remove TinyBundle from AbstractFeatureTest API to fix ClassNotFoundException in camel-itest-karaf

CAMEL-10997: Fixed test due ObjectHelper.isNotEmpty was changed.

CAMEL-10997: Fixed test due ObjectHelper.isNotEmpty was changed.

Add custom valiation logic for twitter credential

CAMEL-10997: Fixed test due ObjectHelper.isNotEmpty was changed.

CAMEL-10986: Add master route policy

CAMEL-10998: deprecate jetty producer

Regen

CAMEL-10791-added option to handle empty directories while unzipping

    • binary
    /components/camel-zipfile/src/test/resources/hello.odt
CAMEL-10791-added option to handle empty directories while unzipping

Upgrade Kubernetes client to version 2.2.7

CAMEL-10791-added option to handle empty directories while unzipping

CAMEL-10791-added option to handle empty directories while unzipping

CAMEL-10791-added option to handle empty directories while unzipping

Upgrade Netty40 to version 4.0.45.Final

Upgrade Netty to version 4.1.9.Final

CAMEL-10986: Add master route policy

CAMEL-10986: Make it easier to extend so we can have a route policy for master component as well.

CAMEL-10986: Make it easier to extend so we can have a route policy for master component as well.

CAMEL-10996: Upgrade kafka to 0.10.2.0

CAMEL-10994: camel-kafka - Allow to configure more options on component level

camel-kafka - Update its default values due kafka changes and add missing option

CAMEL-10994: camel-kafka - Allow to configure more options on component level

CAMEL-10993: camel-kafka should not WARN for each sent message that has no key

Polished docs

CAMEL-10966 Salesforce Maven Plugin doesn't esc...

...ape strings when doing the camel-salesforce:generate phase

This changes the test a bit, let me explain how: there is no need to use

reflection to make a method in the object under test accessible, we can

simply change the visibility of the target method and refactor where

needed. This makes the object under test easier to test and in the end

better in quality.

So I changed the visibility of the `engine` field to package private to

make it accessible from the test, and refactored the initialization of

`VelocityEngine` into `createVelocityEngine` method so that it can be

used in the test. Now this can be used in the `setUp` method of the

test.

To clean up the test a bit I used `Parameterized` runner which is nice

for tests that repeat the same checks over a number of inputs --

parameters, there is a unused field `json` but that's the way the

`Parameterized` runner works: every parameter needs to be used. I've

added `@Parameters(name = "json = {0}, source = {2}")` to make the tests

cases for different parameters more distinct from each other, with IDE

support it is possible to run all or only single test case (set of

parameters)[1].

I also added a JUnit rule that will create and cleanup the temporary

directory, that way the test can be run via different runners in

parallel -- for instance I use Infinitest that runs tests in the IDE in

the background, now I'm sure that those won't interfere with the tests I

run manually. So this makes the test run less prone to outside

influences and less _flaky_.

[1] http://blog.moritz.eysholdt.de/2014/11/new-eclipse-junit-feature-run-subtrees.html

CAMEL-10986: camel-zookeeper-master - Donation of the master component from fabric8 v1

CAMEL-10986: camel-zookeeper-master - Donation of the master component from fabric8 v1