This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Initialisation of "Inline Temp" dialog is too slow - should be as fast as Rename/Extract Variable | ||
---|---|---|---|
Product: | java | Reporter: | markiewb |
Component: | Refactoring | Assignee: | Ralph Ruijs <ralphbenjamin> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.2 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Selfsampler SNAPSHOT
Shows the refactoring preview: It was a really simple inline |
Created attachment 160264 [details]
Shows the refactoring preview: It was a really simple inline
|
Created attachment 160263 [details] Selfsampler SNAPSHOT * Use a large maven project with many snapshot dependencies (perhaps not the culprit) * Wait that the IDE has finished scanning * select a variable within a method and call "inline temp" ACTUAL: it takes more than 10 seconds to see the refactoring preview. The IDE starts scanning the classpath again. Or there is another reason - see the selfsampler snapshot. I do not understand, why it is needed or so slow. The classpath seemed to be up to date: Code completion does not start scanning the classpath again. Inline Rename works also fast. Extracting variable is also fast. It is faster to inline it via copy and paste than to use the inline refactoring. EXPECTED: no scanning is needed, or the scanning time is reduced. Inline is as fast as Rename or Extract. @Ralph: Can you please have a look at it? Product Version: NetBeans IDE Dev (Build 201607010002) Updates: Updates available Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb) User directory: C:\Users\markiewb\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\markiewb\AppData\Local\NetBeans\Cache\dev