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: | Allow nested projects to participate in outer project's logical view | ||
---|---|---|---|
Product: | projects | Reporter: | _ tboudreau <tboudreau> |
Component: | Generic Projects UI | Assignee: | Jan Lahoda <jlahoda> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | jglick, jtulach, phrebejk, ttran, tzezula |
Priority: | P2 | Keywords: | API |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
Simplest possible implementation I could conjure to do project composition
Slightly improved patch - eliminated superfluous FilterNodes Variation which introduces ProjectFactory extension NestedProjectFactory w/ isNestedProject(FileObject), rather than exposing all nested projects |
Description
_ tboudreau
2006-06-13 06:07:49 UTC
Created attachment 30985 [details]
Simplest possible implementation I could conjure to do project composition
Created attachment 30986 [details]
Slightly improved patch - eliminated superfluous FilterNodes
Created attachment 30987 [details]
Variation which introduces ProjectFactory extension NestedProjectFactory w/ isNestedProject(FileObject), rather than exposing all nested projects
BTW, if I'm not explaining this clearly or you don't understand what I'm trying to achieve, let me know. The basic idea is just to let nested projects underneath a project *look* as if they're part of the main project - by adding actions (you can already do that) and nodes to the logical view of the project. It seems to me a very clean solution to the problem of extending projects and project "natures" - and also a problem "natures" doesn't really solve - which is when you have >1, say, UML model or JDNC config or such for a project. BTW, the advantage to the approach in the last patch is we can avoid exposing things like all the projects under the Java module. A project can say it is a project, a nested project (shouldn't be openable on its own), or both. We already have an SPI for extending project nodes under API review. We do not wish to tie it to nested projects specifically, I think; we wish to allow any module to extend any project's logical view for whatever reason. *** This issue has been marked as a duplicate of 72441 *** |