te:
> > Hi Luca,
> >
> > I’ve just encountered an issue when using the date function that gets
> substituted by Log4j 2 and causes the exception below to be thrown.
> >
> > It happens in a number of situations:
> > - when a route definition containing the date
I'll ask the log4j guys, thx for spotting this.
---
Luca Burgazzoli
On Thu, Aug 18, 2016 at 5:37 PM, Antonin Stefanutti
wrote:
> Hi Luca,
>
> I’ve just encountered an issue when using the date function that gets
> substituted by Log4j 2 and causes the exception below to
Hi Luca,
I’ve just encountered an issue when using the date function that gets
substituted by Log4j 2 and causes the exception below to be thrown.
It happens in a number of situations:
- when a route definition containing the date function get logged (in DEBUG
level)
- when an advice is being
t;>>>>>> logging
>>>>>>>>>> > > >> > > > implementation, they should not be included in normal
>>>>>>>>>> component
>>>>>>>>>> > > >> modules
>>>>>>>>>> > > >> > > IMO.
>>>>>
t; >
>>>>>>>>> > > >> > > > The results:
>>>>>>>>> > > >> > > > *./camel/components/camel-atmos [INFO] | +-
>>>>>>>>> > > >> > > log4j:log4j:jar:1.2.17:compile*
>>>>>>>>> > > >> > > > *./camel/components/camel-gora [INFO] | +-
>>>>
>>> > > >> > > >
>>>>>>>> > > >> > > > Should these dependencies be removed?
>>>>>>>> > > >> > > >
>>>>>>>> >
>>>>> > > >> > > log4j:log4j:jar:1.2.17:compile*
>>>>>>> > > >> > > > *./camel/components/camel-gora [INFO] | +-
>>>>>>> > > >> > >
;>> > > >> > > log4j:log4j:jar:1.2.17:compile*
>>>>>> > > >> > > > *./camel/components/camel-jbpm [INFO] +-
>>>>>> > > >> > > > org.slf4j:slf4j-log4j12:jar:1.7.21:compile*
>>>>>> > > >> >
>>> > > >> > > log4j:log4j:jar:1.2.17:compile*
>>>>> > > >> > > > *./camel/components/camel-jt400 [INFO] +-
>>>>> > > >> > > > org.slf4j:slf4j-log4j12:jar:1.7.21:compile*
>
;> > > >> > > > *./camel/components/camel-krati [INFO] | -
>>>> > > >> > > log4j:log4j:jar:1.2.17:compile*
>>>> > > >> > > > *./camel/components/camel-openshift [INFO] | -
>>>> > >
O] +-
>>> > > >> > > > org.slf4j:slf4j-log4j12:jar:1.7.21:compile*
>>> > > >> > > > *./camel/components/camel-scr [INFO] +-
>>> > > >> log4j:log4j:jar:1.2.17:compile*
>>> > > >> > > > *./camel
> > >> > > log4j:log4j:jar:1.2.17:compile*
> > > >> > > >> > > > *./camel/components/camel-krati [INFO] | -
> > > >> > > >> > > log4j:log4j:jar:1.2.17:compile*
> > > >> > > >> >
| -
> > >> > > >> > > log4j:log4j:jar:1.2.17:compile*
> > >> > > >> > > > *./camel/components/camel-openshift [INFO] | -
> > >> > > >> > > > log4j:log4j:jar:1.2.17:compile*
> > >> > > >
omponents/camel-scr [INFO] +-
> >> > > >> > > > org.slf4j:slf4j-log4j12:jar:1.7.21:compile*
> >> > > >> > > > *./camel/components/camel-scr [INFO] +-
> >> > > >> log4j:log4j:jar:1.2.17:compile*
> >>
> >> > > log4j:log4j:jar:1.2.17:compile*
>> > > >> > > > *./camel/components/camel-spark [INFO] | | +-
>> > > >> > > > log4j:apache-log4j-extras:jar:1.2.17:compile*
>> > > >> > > > *./camel/components/camel-spark-rest [INFO] | +-
>> >
; > > > org.slf4j:slf4j-simple:jar:1.7.21:compile*
> > > >> > > > *./camel/components/camel-spring-boot [INFO] | | +-
> > > >> > > > ch.qos.logback:logback-classic:jar:1.1.7:compile*
> > > >> > > > *./camel/components/camel-spring-boot [IN
t; >> > > > *./camel/components/camel-spring-boot [INFO] | | | -
> > >> > > > ch.qos.logback:logback-core:jar:1.1.7:compile*
> > >> > > > *./camel/components/camel-spring-boot [INFO] | | -
> > >> > > > org.slf4j:log
boot-starter [INFO] | | +-
> >> > > > ch.qos.logback:logback-classic:jar:1.1.7:compile*
> >> > > > *./camel/components/camel-spring-boot-starter [INFO] | | | -
> >> > > > ch.qos.logback:logback-core:jar:1.1.7:compile*
> >>
jar:1.1.7:compile*
>> > > > *./camel/components/camel-spring-boot-starter [INFO] | | | -
>> > > > ch.qos.logback:logback-core:jar:1.1.7:compile*
>> > > > *./camel/components/camel-spring-boot-starter [INFO] | | -
>> > > > org.
ponents/camel-spring-boot-starter [INFO] | | -
> > > > org.slf4j:log4j-over-slf4j:jar:1.7.21:compile*
> > > > *./camel/components/camel-zipkin-starter [INFO] | | +-
> > > > ch.qos.logback:logback-classic:jar:1.1.7:compile*
> > > > *./camel/components/ca
ack:logback-core:jar:1.1.7:compile*
>> > > *./camel/components/camel-spring-boot-starter [INFO] | | -
>> > > org.slf4j:log4j-over-slf4j:jar:1.7.21:compile*
>> > > *./camel/components/camel-zipkin-starter [INFO] | | +-
>>
[INFO] | | | -
> > > ch.qos.logback:logback-core:jar:1.1.7:compile*
> > > *./camel/components/camel-zipkin-starter [INFO] | | -
> > > org.slf4j:log4j-over-slf4j:jar:1.7.21:compile*
> > > *./camel/components/camel-zookeeper [INFO] | +-
> > > log4j:log4j:jar:1.2.17:c
gt; > *./camel/components/camel-zipkin-starter [INFO] | | -
> > org.slf4j:log4j-over-slf4j:jar:1.7.21:compile*
> > *./camel/components/camel-zookeeper [INFO] | +-
> > log4j:log4j:jar:1.2.17:compile*
> >
> > On Tue, Aug 2, 2016 at 3:14 PM, Luca Burgazzoli
>
On Tue, Aug 2, 2016 at 3:14 PM, Luca Burgazzoli
> wrote:
>
>> Yep, I meant upgrading log4j for test only, run-time should
>> definitively use slf4j-api (or maybe a custom facade)
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Tue, Aug 2, 2016 at 2:50
gt; real pain as the log4j xml file format is verbose and clunky to work
> > with.
> >
> > Only recently they added support for .properties file but I think they
> > may have changed the syntax slightly (not sure).
> >
> http://stackoverflow.com/questions/22485074/lo
2 is EOL since a year, would it make sense to move to log4j 2 ?
>>
>
> We only use it for testing. No runtime dependency.
>
>
> log4j v2 did not support log4j.properties file so any migration was a
> real pain as the log4j xml file format is verbose and clunky to work
>
2:50 PM, Claus Ibsen
>> wrote:
>> > > On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli <
>> lburgazz...@gmail.com>
>> > wrote:
>> > >> Hello,
>> > >>
>> > >> as log4j 1.2 is EOL since a year, would it make sense to mov
t; >
> >
> > On Tue, Aug 2, 2016 at 2:50 PM, Claus Ibsen
> wrote:
> > > On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli >
> > wrote:
> > >> Hello,
> > >>
> > >> as log4j 1.2 is EOL since a year, would it make sense to move t
e, Aug 2, 2016 at 2:50 PM, Claus Ibsen wrote:
>> > On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli
>> wrote:
>> >> Hello,
>> >>
>> >> as log4j 1.2 is EOL since a year, would it make sense to move to log4j
>> 2 ?
>> >>
>> &g
j 1.2 is EOL since a year, would it make sense to move to log4j
> 2 ?
> >>
> >
> > We only use it for testing. No runtime dependency.
> >
> >
> > log4j v2 did not support log4j.properties file so any migration was a
> > real pain as the log4j xml file f
it make sense to move to log4j 2 ?
>>
>
> We only use it for testing. No runtime dependency.
>
>
> log4j v2 did not support log4j.properties file so any migration was a
> real pain as the log4j xml file format is verbose and clunky to work
> with.
>
> Only recent
On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli wrote:
> Hello,
>
> as log4j 1.2 is EOL since a year, would it make sense to move to log4j 2 ?
>
We only use it for testing. No runtime dependency.
log4j v2 did not support log4j.properties file so any migration was a
real pain as t
:
Hello,
as log4j 1.2 is EOL since a year, would it make sense to move to log4j 2 ?
---
Luca Burgazzoli
Hello,
as log4j 1.2 is EOL since a year, would it make sense to move to log4j 2 ?
---
Luca Burgazzoli
34 matches
Mail list logo