Bug 518187 - Provide DebugListener through OSGi component to decouple
Summary: Provide DebugListener through OSGi component to decouple
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2017-06-13 08:45 EDT by Jens Kuebler CLA
Modified: 2023-07-19 00:08 EDT (History)
1 user (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 Jens Kuebler CLA 2017-06-13 08:45:58 EDT 
The DebugOptionsListener is registered during startup of JavaCore which is premature if you require to load only a class from the bundle. Handling it through OSGI DS enables loading of classes and asynchronously starting the component.

The JavaModelManager contains the debug registration for the Debug options. As a separation of concern this should be a different class. It may then be provided through a declarative service as well.
Comment 1 Eclipse Genie CLA 2019-07-23 17:11:09 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Jay Arthanareeswaran CLA 2019-08-07 02:14:25 EDT 
Jens, thanks for the bug. I am afraid the JDT Core team is busy with Java 13 work and not sure if we can find time for this any time sooner.

OTOH, if you can find time to come up with a patch, one of us can look at it.
Comment 3 Eclipse Genie CLA 2021-07-28 15:15:48 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2023-07-19 00:08:27 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.