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 PM, Claus Ibsen <claus.ib...@gmail.com> 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 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
