The Apache Jenkins build system has built Camel.trunk.notest (build #2736)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2736/
to view the results.
Is it "Lucky Luke" that has non ASCII chars?
You can use \u to specify non ascii chars. We do that in some unit tests.
I remember we have some for german, and also for the Thai elephant
which is named Chang, which is a good beer btw ;)
On Fri, Apr 29, 2016 at 2:49 PM, Siano, Stephan wrote:
>
Hi
I had all the components opened in my IDEA and while reading emails
this morning over a few hours got those fixed. Then besides the
components there was not so many CS errors outside, except for a few
examples. So it turned out it wasn't so much work after all.
I think it was camel-cxf that sp
Is there a JIRA for this that I can use for PRs if I get a chance to go fix
some of the new check style issues?
> On Apr 29, 2016, at 12:45 AM, Claus Ibsen wrote:
>
> I upgraded checkstyle to latest release that supports better lambdas
> so the styling is correct.
>
> But the new rules find n
Hi,
I have found an issue with the camel-csv component. The fix itself is pretty
trivial (a one-liner to use the IOHelper.getCharsetName(exchange)) for an
OutputStreamWriter in the marhaller (the InputStreamWriter in the unmarshaller
already does this).
However I have some difficulties with th
Github user tompahoho closed the pull request at:
https://github.com/apache/camel/pull/957
---
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 en
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/969
---
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 enabl
GitHub user urbanenomad opened a pull request:
https://github.com/apache/camel/pull/970
Previous code was over writing result values
I apologize for my earlier faux pas. I have properly tested this and
verified that it passes the unit test. I also took a more direct solution to
t
Hi
Okay the issue in camel-jetty8 has been fixed.
The source should be ready. And I fixed the CS yesterday.
On Fri, Apr 29, 2016 at 8:47 AM, Claus Ibsen wrote:
> Hi
>
> There is an issue in camel-jetty9 I need to look at on the 2.17.x
> branch after a fix was backported.
>
> On Thu, Apr 28, 201
