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.

Bug 23818

Summary:	Define Java Library <-> Classpath Interaction
Product:	java	Reporter:	Svata Dedic <sdedic>
Component:	Classpath	Assignee:	_ pkuzel <pkuzel>
Status:	RESOLVED WONTFIX
Severity:	blocker
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	TASK	Exception Reporter:
Bug Depends on:	23816, 23828
Bug Blocks:	23798, 23820, 31864, 32701

Description Svata Dedic 2002-05-22 09:10:40 UTC

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.

Comment 1 Svata Dedic 2002-05-22 10:18:41 UTC

Adjusting milestone for planning

Comment 2 _ pkuzel 2003-04-03 15:55:20 UTC

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.

Comment 3 Svata Dedic 2003-04-04 05:35:19 UTC

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.

Comment 4 Jesse Glick 2003-11-23 15:41:38 UTC

Setting subcomponent code -> classpath for easier searching

Comment 5 Jan Pokorsky 2003-11-27 15:00:07 UTC

The projects prototype has been canceled. For more details see
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss