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 200501271900 Classpath can be set only for source folders, not for Web Pages as it is mentioned in UI spec. It should be placed in Wizard (see http://projects.netbeans.org/buildsys/freeform-project-ui-spec-promoe.html#Step_6_Web_Classpath) and in Customizer. Customizer UI spec (http://projects.netbeans.org/buildsys/freeform-project-ui-spec-promoe.html#Classpath) doesn't contain this information and the name should be 'Web Pages' in the list box instead of 'web' to be consistent with Logic view. Jano, could you update UI spec please?
Is this actually necessary to set classpath for web pages? This will increase the manual effort needed to set up the project, and may confuse users, in addition to being error-prone. Petre P., is this really needed in the editor? Or could the editor determine the classpath in another way?
This is only about freeform. There is one step in the wizard, where user can add jars, projects or folder for a specific java source folder on classpath. I don't know, why the user should specify for example jstl.jar and standard.jar or a jar file, which contains only tag files as library, for java root util/src? This is not logical. Yes, user can define "global" classpath when the check box "Separate Classpath for Each Source package folder" will be unchecked in project properties. But then everything has to be propagated on the classpath of web root as well. On the other hand, we have this separation of classpath in the project. Different classpath for web root and for every java source. User can define it by hand in the project.xml, but this is more workaround. There is only missing UI to be defined it. I'm able to get all jars, projects and folders, which are defined for compiling the java roots in the editor. The algorithm is simple. Get compile classpath for webroot (there should be all java roots, but see issue #55702) and find compiling classpath for these java roots and mix all results together. But as I write above, it doesn't seem to me very logical.
Adding UI keyword, please use this keyword for all UI issues.
I commited the changes in the trunk. The UI spec is updated by Jirka Kopsa.
Verified in 200503301800.