[NETBEANS-5627] Gradle project Lookup inconsistent until OpenProjects.open()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 12.5
• Component/s: projects - Gradle
• Labels: pull-request-available
• Assignee: Svatopluk Dedic
• Reporter: Svatopluk Dedic
• Created: 27/Apr/21 09:18
• Updated: 26/Sep/21 07:15
• Resolved: 26/Sep/21 07:14

Description

Gradle fallback support recognizes several plugins from the directory structure (without reading the build.gradle file): groovy, java,  scala, war.

However project Lookup does not contain services for those Plugins, until OpenProjects.open() is called. The Project, however still untrusted, and unevaluated, starts to serve java-related services.

This is inconsistent with project API's philosophy: https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-projectuiapi-base/org/netbeans/api/project/ui/OpenProjects.html

Only certain operations should actually be aware of which projects are "open"; by default, all project functionality should be available whether it is open or not.

In this particular situation, ClassPath.getClassPath(sourceFile, SOURCE) does not return ClassPath even though Gradle fallback support recognizes 'java' and 'java-base' plugins until the project opens in the UI. For the rest of the IDE, the project appears as not having any sources in it - the returned ClassPath is not marked as incomplete, but simply does not exist.

Issue Links

• is related to: NETBEANS-6065 Gradle Tests Leaks Connection to Gradle Daemon
• links to: GitHub Pull Request #2924