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.
The library content form a Classpath for various services. It is expected that the services will require sharing (e.g. automagical inclusion of an item, if it was added for some related service), the classpath provider should support this feature. The provider should be able to filter/convert library contents of a desired type to a ClassPath object(s) with the desired type.
Adjusting milestone for planning
I'm curious if library definition should know about classpath types or its client services. It should be handled by a library reference. Do I understand it correctly that you refer to library reference and the reference should implement a classpath provider interface? Another possible approach is that library content typing is defined by classpath type it's added to.
My idea was that it could be possible to obtain a service using a common interface (e.g. Lookup ;-)) from the library container, but the service itself would be provided by a module and the service's interface would be specified in some other API. This way java module may provide some ClassPath enumerator for libraries -- e.g. instance of o.n.a.java.classpath.PathFactory, or directly o.n.a.java.PathResource/PathContent re. different types: originally the idea was that the user of a library would only "suck up" resources from a path of a given type (e.g. suck only BASIC resources into BASIC path), but I don't think it is really necessary. I would go for the simple case first: classpath's library resources would end up and be typed by whatever path they are placed on, so the Java-specific service for a library would be a single PathResource, probably.
Setting subcomponent code -> classpath for easier searching
The projects prototype has been canceled. For more details see http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss