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'm asking for a review for compatible API change. The target is NetBeans 5.5. The main reason for this change is that we want to use jsp parser, which is javaee5 compatible. Now we used a parser from glassfish. The parser now exclude from the web module classpath "systems" jars, which are part of javaee. For example the system jars include jsf or jstl. The parser then work with these system jars, which are not on the same classloader as the web module. So the ide has to provide this server system classloader to the parser to be able parse pages which use a system jar. These system jars should be expose from the target server through J2EE Platform. I propose to add method that will access the jars for the parser, which are not libraries for the project, but the project needs these libraries. Usually in design time and runtime these jars are a part of the target server. In this time, there is only one client of this api - the jsp editor. /** This method returns the entries, which are needed for parsing jsp files, but are * not directly included in the project (as library). For example there are taglibraries * which are offered by the target server(J2EE Platform), so the project has these entries * on the classpath, but they are not defined by the project. It can return null. */ public abstract File[] getExtraClasspathEntries();
If there are no comments, I'm going commit the changes into release55 branch.
Isn't this issue completed?
Yes, I commited the changes on Thursday.
v.