Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.0-RC-1
-
Fix Version/s: 5.0.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||||
|---|---|---|---|---|---|---|---|
|
|
|
||||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Put SLF4J to JUL bridges in the system classloader | Put JCL/LOG4J to SLF4J and SLF4J to JUL bridges in the system classloader |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Priority | Blocker [ 1 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Link |
This issue blocks |
| Link | This issue blocks PETALSDISTRIB-135 [ PETALSDISTRIB-135 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Fix Version/s | 5.0.0 [ 10631 ] | |
| Description |
Since 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). |
Since 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). |
| Link |
This issue blocks |
| Link |
This issue blocks |
| Link |
This issue blocks |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

This means that all these dependencies can be removed from components, extensions and mutable implementations.
(but if we don't, it's not a problem though)