Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGB5yNmvmoQYkvFPdT2=YWHE2-itRrOErHbPTZb5PfDbQq-giQ@mail.gmail.com>
References: <CAMpNYoY6YbgM-DryKF6bTdxR=YnZ2UzP1VPVMxKz3Sa9GkzY9w@mail.gmail.com>
 <CAGB5yNmvmoQYkvFPdT2=YWHE2-itRrOErHbPTZb5PfDbQq-giQ@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 2 Aug 2016 14:52:46 +0200
Message-ID: <CAGB5yN=4Kr7LqsP95=TL-N8MY0n0ZpLuWD+DR31ntQHzLOuD2g@mail.gmail.com>
Subject: Re: Log4j 2
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Tue, 02 Aug 2016 12:53:13 -0000

Oh and if any migration is needed, then maybe logback is an
alternative than log4j v2?
http://logback.qos.ch


On Tue, Aug 2, 2016 at 2:50 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli <lburgazzoli@gmail.com> 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 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/log4j-2-doesnt-support-log4j-properties-file-anymore
>
>
> And I think I read somewhere that log4j v1 has problems with Java 9.
>
> If migration can be super easy on current 2.18 then it is okay.
> Some kind of migration tool that can covert v1 properties to v2
> properties then that can be doable.
>
> But if not then I would like to postpone this to Camel 3.
>
>
>>
>> ---
>> Luca Burgazzoli
>
>
>
> --
> 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