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.
From the email discussion: If Chris agrees, I'd like to have an option that lets the user display physical source roots under the Packages node. This would be controlled with a checked menu item on the Packages nodes' pop-up menu. This menu item would be off by default; when checked, it would show root folders under the Packages node, with the full path names. -- I disagree. Such display would defeat the purpose of packages node to merge disjoint sources into a logical view. Please describe use cases or scenarios, where this mixed view would serve better than folder view, which has been rejected entirely. -- i don't think this is a good idea either. the problem of being able to figure out which java root is providing which sources may be a problem (or it may not) but i'm not inclined to want to let this kind of option trickle into the Packages node. it might be enough to add a special property editor to the Packages node that opens a dialog with an explorer view of each java root and the packages it contains... but this would be something separate from the Packages node and it wouldn't offer any functionality other than browsing.
Depending on the solution Chris will come up with it may take some longer time to implement it. I am not sure whether we will be able to finish this in time for usability study, but well let's try to do our best.
the solution for this is will be the cutsom property editor (well, i think that's the solution -i'm open to other ideas) and is covered in 28643. for more info see the spec: http://projects.netbeans.org/uispecs/java/JavaProjectsUISpec.html#v.ii figure 23 *** This issue has been marked as a duplicate of 28643 ***
Chris, I don't think the custom property editor will be usable for the real work. Note that custom property editors are modal dialogs. It means that user will open the CPE, browse the structure, perhaps open some source file in editor, but then she has to close it to be able to continue her work. When she needs to browse the structure she has to open the CPE again, ... IMO this makes the per-source-roots view useless for users or at least it can't be used as an equvivalent alternative to merged-roots view.
aha, i see the problem here. this is not meant as an equivallent to the merged-roots view. see mail on dev@projects.
closing as this will be handled by the logical/files views
The current version of Java UI spec does not talk about this problem. Please close issues as Fixed only when the fix was delivered to the project, as everyone else in development group.
closing
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as VERIFIED --->
---> CLOSED
Reorganization of java component