Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
12.0
-
None
-
None
Description
Find Usages (e.g. for a Java class) includes occurrences in downstream Maven artifacts in the local repository (~/.m2), regardless of the Scope selected in the Find Usages dialog. E.g. even when selecting scope "Current File", the Maven repository is still searched. This can be quite slow, because all matching versions of the downstream artifacts (= artifacts having a dependency on the current project) are searched.
Expected behavior: Downstream Maven artifacts should only be included if "Open Projects & Dependencies" or "Current Projects & Dependencies" is selected. Alternatively, there should be an option to include/exclude those.
The current behavior is a major performance problem for me. Taking a typical example case, Find Usages for a class in a medium-sized project takes 45 seconds to complete, with 259 occurrences found, 97 of which in ~25 different versions of three downstream artifacts. (In IntelliJ the equivalent search is instantaneous, by the way.)