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 webapps team needs APIs, which would allow manipulation of Compiled Classes targets, for example: - Creating a new target with a given input fileset, output directory and build options. Options should have reasonable defaults, so they work well even if not specified. - Finding an existing target for a specific source or classpath root - Modidying an existing target - changing the input fileset, output directory and build options - Deleting an existing target
(1) would it be sufficient to create build target with some reasonable default setup then change its options programmatically ? (3) Output directory is OK, input fileset changes will be more restricted: e.g. instead of buildTarget.setInputs(something) it would be more like aSourceTree.assignTo(buildTarget) - to ensure that no two build targets compile the same source.
Yes, all this is fine. Also, there is one more thing that may be needed: getting all Compiled Classes targets. This may be supported directly be the infrastructure, though I am not sure.
Fixed by new ant based build system