[
https://issues.apache.org/jira/browse/NETBEANS-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900437#comment-16900437
]
Laszlo Kishalmi commented on NETBEANS-2714:
-------------------------------------------
[~Furrer] would you create another ticket to have a force reload on Gradle
Project, that would be a quite simple addition.
This issue is also tackles some NetBeans core project manager dependencies. If
the IDE is needed to be rebooted on switching branches, that's not a good sign.
I guess some cache needs to be invalidated in such times.
> NetBeans gradle support does not recognize new subproject creation
> ------------------------------------------------------------------
>
> Key: NETBEANS-2714
> URL: https://issues.apache.org/jira/browse/NETBEANS-2714
> Project: NetBeans
> Issue Type: Bug
> Reporter: Shevek
> Priority: Major
>
> If I switch git branches or otherwise cause a new subproject to appear in a
> gradle project, NetBeans does not recognize that.
> I gather new NB watches the build.gradle(s) for changes, but it appears to
> miss this one.
> This is a fairly common use case - the old gradle plugin did NOT watch for
> changes, and one had to do a manual reload. The new gradle plugin does watch
> for changes, and there is no reload option, so the only way to see a new
> subproject is to restart the whole IDE (grrr, again).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
