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 would like to reuse the implementation of Java resources -- the way they are created and stored in project -- and override the way they are used. It can be done by defining new types of classpath in web module. The UI that lets the user decide how a resource is used should be customizable, it should offer the classpath types defined by the web module. This means that in the web module project the user would be presented with options like: "Use only for compilation", "Deploy to server", "Deploy in web module".
I think it would be useful in general to be able to enhance the Java resource wizard and the appearance of the Java resource node. For example: - The Javadoc module could allow the user to specify the location of the generated javadoc files. - The WebApps module could detect whether a jar file is a tag library and display additional information for the taglib. - The database module could detect whether a jar file is a JDBC driver, and display additional information about the driver.
FYI: The information that I got from that Java team (Tomas Zezula) is that they will not allow us to extend the Java resource. Specifically I wanted: 1) To define my own type of classpath so that anything that would be added to my classpth would automatically also be added to BASIC classpath. Then I wanted to be able to specify what types of classpath should be offered a web module that has web nature. I was told that this is not good (complicated?) to have the BASIC classpath inherit from my classpath. I see this as a design flaw of Java classpath APIs that they do not allow this. 2) (as an alternative when the previous was refused) to add a look for the Java resource and I would then implement my own wizard and store additional properties that would specify how a resource is used in web module. I was told that Java module will not expose an API that would allow me to specify an alternative look. The recomendation that I got was that I should implement Java resoucres in web module from scratch. I am -allowed- to add them to BASIC classpath if I implement PathResource. IMO this is a pitty but I am already working on it since I need to get my job done.
From the discussion with Pavel Buzek, we classified this issue as a task for project infratructure. The Java Module itself can add panels only to its resources, the added panels will not be attached to jar packager resource.
Is there some other issue filed against projects API to cover this problem? Otherwise this one should be reopened and reassigned.
None that I know off.
OK, so I am reopenning it and reassigning to projects infra.
this is not a defect, changing to TASK
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped.
--> VERIFIED