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.
I miss project wide library term definition and guidelines how their resources should be treated (e.g. relatively to various classpath consumers in project). Note that up/down buttons may complicate implementation and user model a lot. What happens if user clicks them at this customizer then at build target classpath customizer and then again in this customizer? Also note that 6.1.1.4 duplicates section 8 dialog description.
the text in 6.1.1.4 was out of date so that's fixed and the use of Libs on the classpath has been updated as well. the two sections supposed to be the same -each of the customizer dialogs is repeated in its specific section. if the user edits a B.S. or R.P. then changes to the Lib. Customizer panel will not be reflected unless the user clicks the default button.
First part is OK. Regarding Mv buttons, how it will behave in relity. Build step will be responsible for keeping a flag whether it was customized and depending on the flag behave: false - use actual (live) libraries order true - use cloned (dead) build step order Default will erase the flag. The flag is implementation detail, you may describe it to user by some other model if it'll be simpler.
added to spec. see description of move up/down buttons in section 8.1.1
verified
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 CLOSED.
Reorganization of java component