Bug 547204 - [null] 'Annotate' not shown for some bundles
Summary: [null] 'Annotate' not shown for some bundles
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-13 04:37 EDT by Frank Benoit CLA
Modified: 2023-07-25 15:10 EDT (History)
1 user (show)

See Also:


Attachments
jar (2.05 KB, application/octet-stream)
2019-05-13 04:37 EDT, Frank Benoit CLA
no flags Details
src (4.04 KB, application/octet-stream)
2019-05-13 04:38 EDT, Frank Benoit CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Benoit CLA 2019-05-13 04:37:44 EDT
Created attachment 278582 [details]
jar

In a project, i have several bundles added and the source is available as well.
But org.reactive-stream and reactor-core, this does not work.

I created those bundles with the bnd-platform tool.
Find the reactive-stream bundles attached.

When opening e.g. Subscriber class, onSubscribe(Subscription s)
Cursor in 'Subscription', Ctrl-1, no action is shown.
Comment 1 Frank Benoit CLA 2019-05-13 04:38:03 EDT
Created attachment 278583 [details]
src
Comment 2 Eclipse Genie CLA 2021-05-03 11:35:42 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 3 Eclipse Genie CLA 2023-07-25 15:10:59 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.