Community
Participate
Working Groups
This can be triggered by: Have a plugin project in you workspace, which defines Automatic-Module-Name. Open the new Java Build Path/Module Dependencies tab of any Java9+ project Select any module and click "Add Reads...". This triggers a search that will throw like this: Thread [Worker-23: Searching modules in workspace] (Suspended (breakpoint at line 2963 in JavaModelManager)) JavaModelManager.getLocalFile(IPath) line: 2963 MatchLocator.locateMatches(SearchDocument[]) line: 1510 JavaSearchParticipant.locateMatches(SearchDocument[], SearchPattern, IJavaSearchScope, SearchRequestor, IProgressMonitor) line: 112 BasicSearchEngine.findMatches(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor) line: 250 BasicSearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor) line: 595 SearchEngine.search(SearchPattern, SearchParticipant[], IJavaSearchScope, SearchRequestor, IProgressMonitor) line: 670 ModuleSelectionDialog.searchAvailableModules(IProgressMonitor) line: 180 ModuleSelectionDialog.access$0(ModuleSelectionDialog, IProgressMonitor) line: 167 ModuleSelectionDialog$1.run(IProgressMonitor) line: 147 Worker.run() line: 63 S.o. assumes that an automatic module is a file, but our implementation also recognizes the source version of this artifact as an auto module.
FWIW, the search is invoked with workspace scope and this pattern: SearchPattern.createPattern("*", IJavaSearchConstants.MODULE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_PATTERN_MATCH|SearchPattern.R_CASE_SENSITIVE);
Bulk move to 4.14
Bulk move out of 4.13
I am not able to reproduce this problem on the following eclipse. version. Can you please confirm whether this problem still exists? Tested on Eclipse SDK Version: 2019-12 (4.14) Build id: I20190923-1800 OS: Linux, v.4.15.0-64-generic, x86_64 / gtk 3.22.30 Java version: 1.8.0_222 The java projects created are having java 11 compliance
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.
