Travis created NETBEANS-2960:
--------------------------------
Summary: Need a force reload action for Gradle projects
Key: NETBEANS-2960
URL: https://issues.apache.org/jira/browse/NETBEANS-2960
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Reporter: Travis
Assignee: Laszlo Kishalmi
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!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
