Confirmed. It works like that from the beginning. Technically we fire a
forlder refresh once the build finishes, but probably we would need to
be more specific when we issue that.
You can file an issue against that, if you wish. The workaround is to
select the build folder and do a Source > Scan for External Changes
On 11/4/19 9:01 AM, Scott Palmer wrote:
I've noticed with NB 11.2 that the Files panel doesn't allow me to browse
all the files. There are folders on my disk that simply don't show up.
They are normal, non-hidden folders. I've looked in the NB messages.log
file and there doesn't appear to be anything that indicates it was having
an issue reading the folders. I can't find any way to force a manual
refresh either.
The folders are where my Gradle build places some generated files, so the
folders may not be initially present when the project opens, however, even
after the folders are created, reopening the project still doesn't show
them. If I exit NB and launch it again, the folders will show - until I do
a build (which may remove and recreate the folders) and then most of the
folders are invisible to NB again.
This is on Windows 10 with NB 11.2 running on JDK 8u202
Just wondering if anyone else can confirm this before I file an issue.
Regards,
Scott
---------------------------------------------------------------------
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
