[GitHub] camel pull request #2463: camel-ftp - SftpOperations should set byte[] inste...

2018-08-09 Thread tadayosi 
GitHub user tadayosi opened a pull request:

https://github.com/apache/camel/pull/2463

camel-ftp - SftpOperations should set byte[] instead of OutputStream …

…for exchange file body

Otherwise simple SFTP-to-File integrations like:


from("sftp://sample@localhost:/in?password=password=true=Shift_JIS;)
.to("file:/tmp/samples-camel/SftpToFileTest/out?charset=EUC-JP");

fails.

The changed code is mostly identical to that of `FtpOperations`.

Thanks!

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

$ git pull https://github.com/tadayosi/camel sftp-conversion

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

https://github.com/apache/camel/pull/2463.patch

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

This closes #2463


commit 4934c380bc8d5d90ca72c7475b647455b2856dfa
Author: Tadayoshi Sato 
Date:   2018-08-10T04:47:45Z

camel-ftp - SftpOperations should set byte[] instead of OutputStream for 
exchange file body




---

[GitHub] camel pull request #2462: autoOffsetReset

2018-08-09 Thread mikadev 
GitHub user mikadev opened a pull request:

https://github.com/apache/camel/pull/2462

autoOffsetReset

Fix value

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

$ git pull https://github.com/mikadev/camel patch-1

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

https://github.com/apache/camel/pull/2462.patch

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

This closes #2462


commit e1bacbd34afb2fa5237a29cd2f3f0b8603a7fef4
Author: elbaz michael 
Date:   2018-08-09T21:54:05Z

autoOffsetReset

Fix value




---

Re: Re-generating source code - Modified source files afterwards

2018-08-09 Thread Claus Ibsen 
Hi

Okay I found the issue; actually it was myself ;)
And have pushed it upstream

On Wed, Aug 8, 2018 at 10:12 AM, Claus Ibsen  wrote:
> On Wed, Aug 8, 2018 at 10:08 AM, Zoran Regvart  wrote:
>> Hi Claus,
>> happens exactly like that on my end, are we using unordered
>> collections for the schemes of the component?
>>
>
> I think the maven tooling may haven been changed recently and I only
> noticed this when I got back from PTO where there were a lot of code
> changes on master branch.
>
> Yeah it smells like unordered list, or a file system that list the
> files in a different order now.
>
> The thing is that a component can have an alternative syntax (https
> instead of http) but the component generally act similar.
> So it smells like either an unordered list issue or that some code was
> changed to not take into account for this alternative syntax issue.
>
> I will log a ticket and investigate this. At first I just wanted to
> know if it was only me or only a mac issue etc.
> https://issues.apache.org/jira/browse/CAMEL-12716
>
>
>> zoran
>>
>> On Wed, Aug 8, 2018 at 8:31 AM, Claus Ibsen  wrote:
>>> Hi
>>>
>>> When I do a full re-gen of the source code via
>>>
>>> mvn clean install -P fastinstall
>>>
>>> Then afterwards I now have 5 modified files
>>>
>>> modified:   
>>> platforms/spring-boot/components-starter/camel-ahc-ws-starter/src/main/java/org/apache/camel/component/ahc/ws/springboot/WsComponentConfiguration.java
>>> modified:   
>>> platforms/spring-boot/components-starter/camel-http-starter/src/main/java/org/apache/camel/component/http/springboot/HttpComponentConfiguration.java
>>> modified:   
>>> platforms/spring-boot/components-starter/camel-http4-starter/src/main/java/org/apache/camel/component/http4/springboot/HttpComponentConfiguration.java
>>> modified:   
>>> platforms/spring-boot/components-starter/camel-mail-starter/src/main/java/org/apache/camel/component/mail/springboot/MailComponentConfiguration.java
>>> modified:   
>>> platforms/spring-boot/components-starter/camel-sip-starter/src/main/java/org/apache/camel/component/sip/springboot/SipComponentConfiguration.java
>>>
>>>
>>> I think some of our Camel maven tooling etc that generates these
>>> files, likely was changed recently and is causing this.
>>>
>>> I wonder if others have these same 5 files modified as well. And if I
>>> do a diff then their modification is "wrong". As its component with
>>> multiple schemes, eg http and https. Where we would use the first
>>> scheme, eg http in the generated file. But now for me it uses the
>>> latter
>>>
>>> - * Whether to enable auto configuration of the http component. This is
>>> + * Whether to enable auto configuration of the https component. This is
>>>
>>>
>>> I wonder if this is platform dependent, eg mac vs linux vs windows etc?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>>
>>
>> --
>> Zoran Regvart
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2