[Bug 358968] policy for configuring logging systems such as commons logging
| Bugzilla Link | 358968 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Sep 26, 2011 16:01 EDT |
| Modified | May 08, 2021 06:02 EDT |
| Blocks | 353168, 400027, 517319 |
| See also | 470662 |
| Reporter | Steffen Pingel |
Description
Mylyn integrates with a number of libraries from Apache and other providers many of which use the Apache commons logging framework. To avoid potentially confusing output to appear on the console Mylyn sets the "org.apache.commons.logging.Log" system property to "org.apache.commons.logging.impl.NoOpLog" which suppresses any output (users can override this behavior by explicitly setting the system property in which case it is not modified).
Unfortunately, the logging configuration affects all consumers of commons logging. This can be problematic if other consumers that are not aware of Mylyn's default configuration intend to configure logging in a different way (e.g. bug 353168).
Since logging is a platform concern it doesn't seem right to have explicit logging configuration in Mylyn. What is the best way to configuring logging? Should there be support in platform? Should each logging system be configured by separate bundles that are included on a distribution package level? Any other suggestions?
Related discussions and bugs: \
- Discussion about SLF4j: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05659.html\
- Logging output in EPP Java package: 340312\
- Common logging service in platform: bug 292135\
- Use SLF4J for p2: bug 338232\
- Bridging legacy logging APIs: http://www.slf4j.org/legacy.html