Netbeans 26 does not recognize kotlin gradle projects until gradle editor support is manualy activated
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 26 latest release candidate
### What happened
After installing NetBeans 26, I chose File->Open Project and navigated to the folder with my project. But it wasn't recognized as a project folder; I couldn't open it.
I tried creating a brand new gradle application project (using java 24), and this project DOES show up as a valid gradle project.
Comparing the old and new project, I noticed that my project uses kotlin (and hence has a `settings.gradle.kts` file) whereas the newly-created project has a `settings.gradle` file. So it seems the problem is related to kotlin-specific gradle projects.
To test this, I created a zero-byte file named `settings.gradle`. Upon doing this, NB26 does detect the project and can open it correctly.
So the issue doesn't seem to be with processing kotlin gradle projects, just detecting them.
(Unfortunately the command-line `gradlew` application doesn't like having that empty `settings.gradle` file there and generates errors; I'm still trying to find a setup that works for both NB26 and the command line.)
### Language / Project Type / NetBeans Component
Gradle
### How to reproduce
Attempt to open a Gradle project that has a `settings.gradle.kts` file instead of a `settings.gradle` file
### Did this work correctly in an earlier version?
Apache NetBeans 25
### Operating System
Windows 11 24H2
### JDK
Java 11, Java 24
### Apache NetBeans packaging
Apache NetBeans binary zip
### Anything else
- I have tried both the binary zip and the "Friends of Netbeans" windows installation, same behavior in both.
- The project in question uses gradle 8.13
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Start by tracing NetBeans' Gradle project detection for the settings.gradle.kts and settings.gradle files, using the reproduction described in the issue. Done means a Kotlin Gradle project opens without manually activating Gradle editor support, while the command-line gradlew application continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100