Slow completion and insertion into a gradle project
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 20 release candidate
### What happened
Code completion, and especially code insertion, is much slower with a Gradle project than with a Maven project.
### How to reproduce
Just clone the https://github.com/philippefichet/slow-netbeans-example repository and see how long it takes to complete and insert code in the "src/main/java/com/github/philippefichet" class.
/OneEntity.java" class.
On line 17, do this between "return new Str" and "ing();" and complete with the "String (java.lang)" propotition
In the Maven project, insertion is fast, whereas in the Gradle project it's much slower.
A JFR screenshot for Gradle and Maven and an animated screenshot for Gradle and Maven are available in the repository.
### Did this work correctly in an earlier version?
No / Don't know
### Operating System
Edition: Windows 10 Professionnel, Version: 22H2, Build: 19045.3693
### JDK
Zulu21.28+85-CA
### Apache NetBeans packaging
Apache NetBeans binary zip
### Anything else
Slowness is less noticeable under Linux, but still seems to be present.
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Clone the linked slow-netbeans-example repository and reproduce completion and insertion in src/main/java/com/github/philippefichet/OneEntity.java, especially line 17 between "Str" and "ing();". Compare the Gradle and Maven behavior using the supplied JFR and animated screenshots; done means identifying and addressing the Gradle-specific delay while preserving fast Maven behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100