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.
[This was pull from semi-related issue #42151 where it was determined to be a seperate enhancement request.] In NB 3.6, my projects were organized so that they were all in seperate Java packages. With some packages being used by more than one Project. Because of this I had laid the files out on the disk in one src tree, and used only the package directories to keep them seperate. I mounted the source tree once in NB3.6. I like the way NB4.0 Projects are going now though. And I just recently split out all the projects into different project directories with their own 'src' directory. but what I reall miss is that 'overlayed' look at the sources. Would it be possible to have (maybe a seperate tab in the file browser) a view of your sources where the main project, and all the sub or dependent projects sources are overlayed on top of each other so that there is only one package hierarchy? Example: Given Projects: A/ src/ com/ acme/ projA/ A.java B/ src/ com/ acme/ projB/ B.java Utils src/ com/ acme/ Utils/ foo.java bar.java Instead of seeing a tree like: A com.acme.projA A.java B com.acme.projB B.java Utils com.acme.Utils foo.java bar.java Could we see: com acme projA A.java projB B.java Utils foo.java bar.java
Please involve the refactoring team in design decisions - this would have impact on refactoring actions.
Not for 4.0. May consider some kind of "classpath browser" for a future release, but no concrete plans yet.
There is a classpath browser in 4.1 builds now, but not overlaid. There are a number of thorny problems arising from trying to overlay folders like that, because of complex listening behavior, and ambiguous semantics of modification operations (e.g. Delete on a folder), so we are not currently planning this, though it remains an possibility.
I understand that operations which might need to know more about where the file lives (ie. delete) might not get that info as easily in this view. Since I proposed it as an addtional 'view' of the files, not the only view, though I would think that those actions could just not be available in that view. Still figuring out which actions those are could be work. Thanks for considering this.