[
https://issues.apache.org/jira/browse/NETBEANS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974008#comment-16974008
]
Andrea Paternesi edited comment on NETBEANS-2960 at 11/14/19 8:22 AM:
----------------------------------------------------------------------
This lack of feature is real annoying. Right now the only way to force a
project reload is to put a blank space into build.gradle and save the file.
This should be implemented as it is now is a waste of time.
Thanks.
was (Author: patton73):
This lack of feature is real annoying. Right now the only way to force a
project reload is to put a blanck space into build.gradle and save the file.
This should be implemented as it is now is a waste of time.
Thanks.
> 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
> Affects Versions: 11.0, 11.1, 11.2
> Reporter: Travis
> Assignee: Laszlo Kishalmi
> Priority: Minor
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
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
