Bugzilla – Full Text Bug Listing
| Summary: | tons of new debug messages in console from help system | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> | ||||
| Component: | User Assistance | Assignee: | platform-ua-inbox <platform-ua-inbox> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cgold, gunnar, ken, pwebster, remy.suen | ||||
| Version: | 3.6.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
David Williams
Created attachment 178583 [details]
screen copy/paste from console window.
almost a thousand messages :)
(from one or two clicks)
May be related to bug 316621. (In reply to comment #2) > May be related to bug 316621. Interesting ... and we do just now have a "full set" of SLF4J in 3.6.1 EPP packages. To cross reference, see bug 322929 for the EPP problem that led to including the SLF4J logging bundle. Just cross-posting my comment from bug 316621. FWIW, the default SLF4J/Logback configuration is *full* debug logging to console and that's likely what happening here. Everybody that gets the console log message is likely running with SLF4J + Logback bundles. There are multiple options available. 1. Point to default log configuration which disables logging. This can be done via a system property pointing to a log config file. It might also be possible to provide a default config via a fragment. 2. Upgrade to SLF4J >= 1.6 to avoid the dependency on Logback. Since 1.6.0 SLF4J is able to run without a logging implementation. It will just emit a single warning upon start up and discard all logging afterwards. 3. Don't install SLF4J at all. That might only be possible if no other bundle is importing SLF4J api. The Jetty bundle in Orbit is capable of running without SLF4J. Not sure how to close this (dup? worksforme?) ... was a result of an attempted fix to bug 322929 which was backed out so this is no longer an issue. *** Bug 316621 has been marked as a duplicate of this bug. *** I'm sorry. I don't see how to fix this issue of extensive DEBUG output to the console from the information given here. I am using the Eclipse org.eclipse.help.ui in an RCP application and doing nothing special. This problem did not used to happen. Of the multiple options: 1. I don't want the output at all, so sending it to a file is not a good choice. Moreover, I don't understand how to implement the suggestion. More specifically, what would I set. 2. _How_ do I get 1.6 into my RCP app? I am using Eclipse 3.6.0 and the only org.slf4j.api available is 1.5.11. 3. Since the .product adds org.slf4j.api as a required dependency, it doesn't seem this would help. I would just like to get rid of all this output from a plug-in which is not my plug-in. If it is going to do that by default, there should be documentation on how to override it. Maybe there is but I haven't found it. I apologize if I am posting this in the wrong place. Any help would be appreciated. Thanks. I'm trying to understand the history of this bug. The comments suggest that this was a regression caused by a fix to bug 322929 and the problem no longer occurs, however your last comment indicates that the problem does still exist. What version of Eclipse are you using to develop your RCP? Do you have a scenario that would enable me to reproduce the problem, I don't see it when running the 3.7 or 4.1 SDK. Chris, Thanks for your interest. I am using 3.6.0. I would rather not develop with a non-released version. Judging from the comments here, it still appears to happen with 3.6.1. I could upgrade to 3.6.2 (if that helps) though upgrading to a new minor version still typically takes some effort (a day or so) for me to get things working again. Can you try 3.6.2 and see if the issue is fixed? (In reply to comment #11) > Can you try 3.6.2 and see if the issue is fixed? OK. It will be a few days before I can get to it though. Do you know if it has the 1.6.0 SLF4J, which is supposed to fix the problem? I'm not familiar with how exactly the problem got fixed. This bug is in the area of User Assistance so it falls under my area of expertise but in this case the problem was fixed/went away without any involvement on my part. Since no-one else is still reporting this problem and the original reporter considers it to be resolved it seems likely that 3.6.2 will fix the problem for you. If it doesn't I can investigate. I updated to Eclipse 3.6.2 and the problem appears to have gone away. FYI: org.slf4j.api no longer appears as a required dependency in the .product (which uses org.eclipse.ui.ide). Also ch.qos.logback.xxx (where xxx = classic, core, slf4j) no longer appear. I'm not quite sure why the status for this bug is RESOLVED INVALID. It seemed pretty valid to me, but does appear to be resolved. Thanks for your help. I've changed the resolution to WORKSFORME which covers the case where something was broken in the past but is now working. |