This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : e866b2d563a1 ] [ JDK VERSION : 1.7.0_40 ] STEPS: * Tried with project https://github.com/ricardolonga/compras ACTUAL: Folders inside 'Web Page' does not have subnodes (The IDE treats it as empty). EXPECTED: Folders inside 'Web Page' should have subnodes, with the content as seen in Files view.
Created attachment 143479 [details] Sample image As you can see in this image, the nodes for some folders are not expandable as expected.
reassigning to j2ee/maven for evaluation
I've got the same problem (was checking current state of the latest dev build of NetBeans). Attaching minimal MAVEN project to reproduce the problem and screenshot for it.
Created attachment 143520 [details] Trial MAVEN project
Created attachment 143521 [details] False-empty folder
Thanks guys, I'm able to reproduce the problem using project from comment 4. I'm on it..
*** Bug 239835 has been marked as a duplicate of this bug. ***
Seems to be caused by small change in Datasystem API: core-main #ed1b861c4c90 (reverting the change is fixing the issue) Although not sure if the change-set should be reverted or if the Nodes API needs to be improved with respect to it. I don't really understand what's going on in all these kinds of Nodes but if you check class WebPagesNode from maven.j2ee (line 76), you will be able to see that without the change-set calling orig.getChildren() returns correct folders/files (and instance of orig is usually DataFolder.ClonedFilter), but after applying it "orig instances" are DelayedNode in some cases and they are returning Children.Empty which results in the missing folders/files in the Project View. Reassigning to Datasystem API for further evaluation, CCing Honza as owner of Nodes API.
http://hg.netbeans.org/core-main/rev/b91f95e0d358 Reverting core-main #ed1b861c4c90. WebPagesNode doesn't expect that children of its original node can be changed, so it cannot be used with DelayedNode. There can be more similar cases in other modules, so the safest solution is to revert the change. I'm very sorry for the inconvenience.