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.
Design an API for project outputs (targets, recepies, etc.) -- how to represent a target, dependencies between targets, relation to sources, etc.
Jan posted a mail about user interface concerning targets. http://projects.netbeans.org/servlets/ReadMsg?msgId=330624&listName=dev
remaining parts for M3: 1. Build targets dependencies checking (Test for cyclic build target dependencies)-Done 2. Timestamps checking enhancements 3. Use dependency (covered separately by 23291) 4. Interproject references (for build dependencies) -- depends on 23294 5. Dependency Cache (covered separately by 21298)
Must-have features for milestone3, have impact on APIs (at least potential).
The ability to query mime types for output is provided as part of the projects API. Each output is a container supplying a content descriptor with the ContentDescriptor.MIME_PROJECT_OUTPUT mime type. A query of the form project.getContainersList().search(ContentDescriptor.MIME_TYPE_OUTPUT) will yield the set of output containers. Each build target may also specify additional mime types representing the output of the build target. Thus another build target may execute the query described above first to obtain all build targets and then perform an additional query on the result to search for a mime type which can be used as input for the build target. The query and defintion mechanisms already exists and thus I am closing this task.
closing, it's done