Bug 544895 - Empty class name in 'Adapters for contextual launch'
Summary: Empty class name in 'Adapters for contextual launch'
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.11   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-27 14:38 EST by Karsten Thoms CLA
Modified: 2023-04-03 09:12 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 Karsten Thoms CLA 2019-02-27 14:38:13 EST 
In the plugin.xml of org.eclipse.jdt.debug.ui there are 3 adapter factories for 'Adapters for contextual launch'. They have all an empty 'class' attribute, which raises a warning:

   <factory class=""

Either provide an appropriate class or remove the attribute.
Comment 1 Sarika Sinha CLA 2019-02-28 04:53:07 EST 
It was added as part of Bug 54946, Not sure why was it added with empty factory classes.
Comment 2 Karsten Thoms CLA 2019-02-28 06:11:45 EST 
Bug or feature? Isn't 'class' mandatory? Can there be a simple factory class inserted to resolve the warnings?
Comment 3 Eclipse Genie CLA 2021-02-18 05:18:58 EST 
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-04-03 09:12:16 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.