Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365860 - References search not working - "no JRE" message
Summary: References search not working - "no JRE" message
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 05:03 EST by john.carter-9wt2bu2 CLA
Modified: 2023-04-01 02:02 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description john.carter-9wt2bu2 CLA 2011-12-07 05:03:33 EST
Build Identifier: 20110916-0149

Hi,

When I try to search references (in project or workspace), Eclipse found 0 references and return me (in the search pannel) the message "0 references in workspace (no JRE)".

I'm on a large project, imported from a svn repository with a subclipse checkout. I'm using a .classpath from someone else (so, not the original created by Eclipse). This problem happen in "separate folders for src & class" mode and in "project folder as root for src & class" mode.

An other detail : in the "Select Main Type" dialog for Main class selection (in Run Configurations), I didn't have the class I would to use. Now it appearing, but I don't know how/why.

Is it a bug ? Or something else with a not really clear error message ?

Reproducible: Always
Comment 1 Dani Megert CLA 2011-12-07 07:06:25 EST
The "no JRE" is not a message but simply indicating that it did not search the JRE. Your problem looks like a wrong Java build path. Make sure
- you don't have build path errors on your project
- all folders that contain code are on the Java build path
Comment 2 Ed Willink CLA 2023-04-01 02:02:15 EDT
https://github.com/eclipse-jdt/eclipse.jdt.ui/issues/508 raised to clarify the "No JRE" text.

I encountered a similar problem of no matches from perhaps just one plugin. It eventually went away after a clean-all restart clean-all.