matthiasblaesing commented on PR #7346:
URL: https://github.com/apache/netbeans/pull/7346#issuecomment-2088833111
@mbien my understanding is, that commons-logging will detect Log4j and SLF4J
on the classpath. If it finds them, it will use one of these. The problem is,
that the class loader commons-logging uses is the thread context class loader,
which can see all resources of all modules of NetBeans. Later Instantiation
will fail because there is not dependency from commons-logging to SLF4J
established.
The detection can be observed here:
```
[LogFactory from org.netbeans.modules.netbinox.NetbinoxLoader@244303269]
Checking if class 'org.slf4j.Logger' is available in class loader
org.netbeans.modules.netbinox.NetbinoxLoader@244303269
[LogFactory from org.netbeans.modules.netbinox.NetbinoxLoader@244303269]
[LOOKUP] SLF4J detected. Loading the SLF4J LogFactory implementation
'org.apache.commons.logging.impl.Slf4jLogFactory'.
```
The load failure is the stack trace.
We could also move SLF4J to the platform cluster, change the Manifest of
commons-logging to depend on it and it would work, but from my POV it is nuts
to log commons-logging -> SLF4J -> JUL, if you can go directly to
commons-logging -> JUL.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
