Bug 431878 - Add all Runtime plugins to General > Tracing preference page
Summary: Add all Runtime plugins to General > Tracing preference page
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 440120
Blocks:
  Show dependency tree
 
Reported: 2014-04-03 04:55 EDT by Szymon Ptaszkiewicz CLA
Modified: 2015-05-18 06:14 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Ptaszkiewicz CLA 2014-04-03 04:55:05 EDT 
If a plugin provides .options file, it is possible to enable tracing for this plugin via General > Tracing preference page. We should add all Runtime plugins to this preference page to make it easier to debug it.
Comment 1 Thomas Watson CLA 2014-04-03 08:45:03 EDT 
Bundles should not be added to the page unless they register a DebugOptionsListener so they can dynamically react to trace options when they are enabled after the platform is up.  That is what the extension point org.eclipse.ui.trace.traceComponents is for, to inform the UI that a bundle can listen to dynamic trace option changes.

I do not disagree with the overall theme of this bug, but it does require work on the part of each bundle.  For example, I just enabled dynamic trace options in the framework with bug 431052
Comment 2 Szymon Ptaszkiewicz CLA 2014-04-03 09:08:33 EDT 
(In reply to Thomas Watson from comment #1)
> Bundles should not be added to the page unless they register a
> DebugOptionsListener so they can dynamically react to trace options when
> they are enabled after the platform is up.  That is what the extension point
> org.eclipse.ui.trace.traceComponents is for, to inform the UI that a bundle
> can listen to dynamic trace option changes.
> 
> I do not disagree with the overall theme of this bug, but it does require
> work on the part of each bundle.  For example, I just enabled dynamic trace
> options in the framework with bug 431052

Thanks Tom! I was not aware that listener is also needed. It does indeed require more work that I initially thought. I will move the bug back to the bucket until I find more time to tackle this.
Comment 3 Markus Keller CLA 2014-04-07 06:07:56 EDT 
(In reply to Thomas Watson from comment #1)
> Bundles should not be added to the page unless they register a
> DebugOptionsListener so they can dynamically react to trace options [..]

Filed bug 432143 to document this.
Comment 4 Dani Megert CLA 2015-03-22 12:50:54 EDT 
What's the plan for 4.5?
Comment 5 Szymon Ptaszkiewicz CLA 2015-04-23 05:53:35 EDT 
(In reply to Dani Megert from comment #4)
> What's the plan for 4.5?

I do not think we can finish this for 4.5.
Comment 6 Szymon Ptaszkiewicz CLA 2015-05-18 06:12:49 EDT 
I have never come across a need to use debug options from the remaining plugins, so I consider this low priority that could be done only for the sake of completeness rather than because of a real need to have it there.