Petals Distribution

Put JCL/LOG4J to SLF4J and SLF4J to JUL bridges in the system classloader

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.0-RC-1
  • Fix Version/s: 5.0.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Since PETALSESBCONT-424, slf4j-api and slf4j-jdk14 will be introduced in the system classloader (see comments).
    It makes sense to also include jcl-over-slf4j and log4j-over-slf4j that contains classes that replace the commons-logging and log4j classes.

    Because slf4j has a very strict policy about changing API, we can be assured that putting them in the system classloader should not introduces bug.
    Basically we will use latest version of 1.7.21 that is backward compatible with slf4j api at least since 1.6 (which is very old).

    Show
    Since PETALSESBCONT-424, slf4j-api and slf4j-jdk14 will be introduced in the system classloader (see comments). It makes sense to also include jcl-over-slf4j and log4j-over-slf4j that contains classes that replace the commons-logging and log4j classes. Because slf4j has a very strict policy about changing API, we can be assured that putting them in the system classloader should not introduces bug. Basically we will use latest version of 1.7.21 that is backward compatible with slf4j api at least since 1.6 (which is very old).
  • Environment:
    -

Issue Links

Activity

People

Dates

  • Created:
    Tue, 31 May 2016 - 13:16:32 +0200
    Updated:
    Wed, 1 Jun 2016 - 11:20:46 +0200
    Resolved:
    Wed, 1 Jun 2016 - 11:20:46 +0200