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.
Mounting a Jar/Zip FileSystem in NB3.6 is like adding the Jar/Zip filesystem in the classpath for compiling sources in NB4.0 But Mounting a Jar/Zip filesystem in NB3.6 (in the default project) need following steps: 1. Right-Click on FileSystems' node 2. Mount | Archive Files 3. Browse through your disks to select the jar/zip file 4. Click on Finish to close the file browser But mounting a Jar/Zip FileSystem in NB4.0 need the following steps; 1. Right-click on your project's node 2. Properties 3. Select Build | Compiling Source in the left panel 4. Click on Add Jar on the Right Panel 5. Browse through your disks to select the jar/zip file 6. Click on Open to close the file browser 7. Click on OK to close the Project Proterties As you can see, Mounting a JAR/Zip FileSystem was easier under NB3.6. So, I propose the following: 1. When you right-click to the project's node have possibility to add a jar/zip file in the compiling source classpath 2. When you right-click to a project's node have possibility to mark it as subproject of the main one. 3. When I right-click on Source Packages and select Properties, open the Project Properties with the Build | Compiling Sources Selected. 4. When I right-click on Test Packages and select Properties, open the Project Properties with the Build | Compiling Tests Selected.
Jano please comment on what you want to implement. If something (Not in D of course) and reassign back to me.
IMHO, this has to be done for NB 4.0.
I agree. First impressions are important. Failure to create a good impression of the new projects system will create grumpy or reluctant users beyond just the 4.0 release.
Could you give me you decision about that issue ? I have not seen any comments of Jan Rojcek.
We won't implement this for NB4.0. In subsequent release, we would most likely introduce a "Libraries" node that displays libraries underneath every project node and permits the user to add libraries to project more quickly than through the project properties.
We decided not to implement 1). Will file enhancement for 2) if not already in issuezilla. 3) and 4) implemented Checking in j2seproject/src/org/netbeans/modules/java/j2seproject/ui/Bundle.properties; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/Bundle.properties,v <-- Bundle.properties new revision: 1.21; previous revision: 1.20 done Checking in j2seproject/src/org/netbeans/modules/java/j2seproject/ui/J2SECustomizerProvider.java; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/J2SECustomizerProvider.java,v <-- J2SECustomizerProvider.java new revision: 1.12; previous revision: 1.11 done Checking in j2seproject/src/org/netbeans/modules/java/j2seproject/ui/J2SEPhysicalViewProvider.java; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/J2SEPhysicalViewProvider.java,v <-- J2SEPhysicalViewProvider.java new revision: 1.28; previous revision: 1.27 done Processing log script arguments... More commits to come... Checking in j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/Bundle.properties; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/Bundle.properties,v <-- Bundle.properties new revision: 1.34; previous revision: 1.33 done Checking in j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/J2SECustomizer.java; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/J2SECustomizer.java,v <-- J2SECustomizer.java new revision: 1.14; previous revision: 1.13 done Processing log script arguments... More commits to come... Checking in project/src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java; /cvs/java/project/src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java,v <-- PackageViewChildren.javanew revision: 1.32; previous revision: 1.31 done
Filled issue #48152. For the rest of this issue.
3) and 4) verified in custom 20040901.