ebug)...
>
> Björn
>
>
>
>
> Von:Claus Ibsen
> An: users@camel.apache.org
> Datum: 28.11.2018 18:29
> Betreff:Re: readLockLoggingLevel File Component
>
>
>
> Hi
>
> Yeah you are welcome to provide a fix via a github PR
> h
: readLockLoggingLevel File Component
Hi
Yeah you are welcome to provide a fix via a github PR
https://github.com/apache/camel/blob/master/CONTRIBUTING.md
If you are a bit lazy you can even just do the PR by editing the
source file from the github web ui directly
On Wed, Nov 28, 2018 at 2:34 PM Zoran
Hi
Yeah you are welcome to provide a fix via a github PR
https://github.com/apache/camel/blob/master/CONTRIBUTING.md
If you are a bit lazy you can even just do the PR by editing the
source file from the github web ui directly
On Wed, Nov 28, 2018 at 2:34 PM Zoran Regvart wrote:
>
> Hi Björn,
>
Hi Björn,
sounds like a great contribution, we love those :)
zoran
On Wed, Nov 28, 2018 at 1:19 PM wrote:
>
> Hi,
>
> one little thing...
> I have noticed that in the javadocs, documentations,... for the the
> property readLockLoggingLevel in the File Component, respectively in the
> class
Hi,
one little thing...
I have noticed that in the javadocs, documentations,... for the the
property readLockLoggingLevel in the File Component, respectively in the
class FileChangedExclusiveReadLockStrategy the default is described as
'WARN'. But in the implementation it is 'DEBUG'. It could
