Bug 578814 - Missing function name in doFind warning message
Summary: Missing function name in doFind warning message
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-17 17:37 EST by Omar Sweidan CLA
Modified: 2024-02-12 15:51 EST (History)
0 users

See Also:

Attachments
screenshot (156.73 KB, image/jpeg)
2022-02-17 17:38 EST, Omar Sweidan CLA 		no flags Details
View All 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 Omar Sweidan CLA 2022-02-17 17:37:13 EST 
Hello, team!

I get an error message when trying to build my OSGi component (see attachment), but it is rather strange that the function name which is not found by doFind() is missing from it. Can you please fix this? Also, what is the reason for this message in the first place? Is it because bindJobEngine function is static?


-- Configuration Details --
Product: Eclipse IDE 4.22.0.20211202-1200 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.pde 3.14.1100.v20220216-2111
Comment 1 Omar Sweidan CLA 2022-02-17 17:38:17 EST 
Created attachment 288072 [details]
screenshot
Comment 2 Eclipse Genie CLA 2024-02-08 06:12:38 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 3 Omar Sweidan CLA 2024-02-12 15:51:46 EST 
Is this bug resolved?