[NETBEANS-2960] Need a force reload action for Gradle projects

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 11.0, 11.1, 11.2
• Fix Version/s: 11.3
• Component/s: projects - Gradle
• Labels: pull-request-available
• Assignee: Laszlo Kishalmi
• Reporter: Travis
• Created: 05/Aug/19 22:31
• Updated: 03/Nov/20 15:47
• Resolved: 23/Nov/19 19:51

Description

I have a multi-project gradle build with a settings.gradle implementation that auto-detects the subprojects.  So whenever a subproject gets added/removed/renamed (either directly, or as the result of a git branch checkout), the root project build.gradle and settings.gradle do not need to be modified at all.

Currently, the gradle support assumes that projects only need to be reloaded when build.gradle or settings.gradle change, but my build breaks this assumption.

So the behavior in my case is that I am not even able to manually browse to a new subproject and open it, until after I make a meaningless edit to build.gradle or settings.gradle.  The new subproject folder is not even recognized as a gradle project in the "open project" dialog until I have touched one of those files.

This behavior is broken.  Ideally, projects that come and go would automatically get noticed, and the IDE would update immediately.  But assuming that's non-trivial to implement, it would be acceptable to simply add a manually-triggerable "force project reload" action somewhere in the GUI, so that the user can get back into a good state without the need to touch any files.

 

Thanks!

Issue Links

• is related to: NETBEANS-2714 NetBeans gradle support does not recognize new subproject creation
• links to: GitHub Pull Request #1634