The Apache Jenkins build system has built Camel.2.14.x.notest (build #37)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/37/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #2210)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2210/
to view the results.
I think the is a good approach.
Best,
Christian
On Mon, Nov 3, 2014 at 8:05 PM, Daniel Kulp wrote:
>
> I went ahead and fixed this more “properly”.
>
> Basically, I updated the Spring version range in the bundle manifests to
> allow 4.x for the imports. It IS possible (with a BUNCH of restric
I went ahead and fixed this more “properly”.
Basically, I updated the Spring version range in the bundle manifests to allow
4.x for the imports. It IS possible (with a BUNCH of restrictions) to use
Spring 4 in OSGi, just not with spring-dm. Thus, allowing the import is
important.
However,
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/314
CAMEL-7993 Add brackets to log statement
Otherwise the file name will not be printed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinear
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/313
CAMEL-6099 Add chmod option to file producer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-6099
Alternatively you ca
