https://bugs.eclipse.org/bugs/show_bug.cgi?id=365860 reported confusion with the "No JRE" comment at the end of Java searches.

This is now much more confusing since the text certainly implies a problem rather than a description.

I encountered a similar problem of no matches. (It eventually went away after a clean-all restart clean-all. It was as if a filter had been applied to the particular plugin that should have been giving results.) Since the problem occurred on a re-built Windows laptop the suggestion of a bad classpath seemed plausible, so I searched hard and spotted "no JRE" and Googling highlighted the observations that Java 11 onwards has no JRE, so I wasted a lot of time trying OpenJDK and then trying to overlay a JRE in traditional fashion. Complete waste of time of course caused by the very misleading message.

Please change to perhaps "omitting JRE" that is clearly descriptive rather than the imperative "no JRE".