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.
ProjectRunner has the ability to debug but not profile. This seems like an omission, since AFAIK these are very similar structurally: you start the JVM with some special options but otherwise run the program normally. Perhaps this is rather a problem in the Profiler, since for some reason that I have not yet figured out, it has a completely different mechanism for running project actions than the debugger. Whatever the case, it does not appear to be integrated with CoS at all. I am trying to figure out what would be needed for autoproject to be integrated with the Profiler (one of the main selling points of the IDE to a typical autoproject user!), preferably making it work as much as possible like run and debug, which already use ProjectRunner; profiler.j2se is much larger than I would have expected and the purpose of most of the source is a mystery to me so far.
A relatively small ProjectTypeProfiler in global lookup turned out to be sufficient to get basic profiler integration working with automatic projects. In order to then tie this into CoS, I needed a small Ant script using <translate-classpath>, which you can see in http://hg.netbeans.org/main/contrib/raw-file/tip/autoproject.profiler/release/autoproject-profile.xml Obviously for use in ProjectRunner this would need to be expanded with some additional properties.