Gradle stores some settings into .gradle which are later marked by MS Java Ext pack as modified project
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 17 release candidate
### What happened
Created Gradle project with subprojects using VSNetBeans 16.0.301 and OCI tooling. This is done in coexistence with MS Java Ext Pack (JDT). Later MS Java reports as problem that Gradle project files was modified and needs to be reloaded to make it effective. It looks like some recent change or regression on NBLS side.
It is not shown when project is open for 2nd time, just after its creation when OCI powered Vulnerabilities audit completes.
Using VSNetBeans 16.0.301
### How to reproduce
_No response_
### Did this work correctly in an earlier version?
Apache NetBeans 15
### Operating System
macOS
### JDK
GraalVM 22.3.0 JDK17
### Apache NetBeans packaging
Apache VSNetBeans for VSCode
### Anything else
_No response_
### Are you willing to submit a pull request?
Yes
### Code of Conduct
Yes
Contributor guide
Assessment
This issue has not been assessed yet.