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.
Summary: | Composite PathResource support | ||
---|---|---|---|
Product: | java | Reporter: | _ pkuzel <pkuzel> |
Component: | Unsupported | Assignee: | Tomas Zezula <tzezula> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | API |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ pkuzel
2003-06-19 13:08:00 UTC
Hmm ;) Could you be a little more specific on what data do you need to construct such for ? I can think about a PathResource which sits on top of a FileSet - or other such collection w/ notification. However the PathResource's Lookup would be empty (it would be a "virtual" PathResource). Or maybe construct a composite PathResource from an existing PathContent ? Oh, it's already planned. Can I also read the explanation what the RFE is about so I know what is actually planned ? PathContent is AFAIK dead. I have list of path resources backgrounded by fileobjects (folders and jars) and need to create composite path resource. You are right that the fileobjects might be better input parameter than PathResources (created from fileobject). Fixed. See the ClassPaths.createPathResource (FileSet) As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as VERIFIED ---> ---> CLOSED |