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.
Using NB 5.0 Q Build of 20051013/Milestone9/JDK5U4/WinXP I can no longer Profile one of the projects used in the Profiler Tutorial: http://www.netbeans.org/kb/articles/nb-profiler-tutor-8.html. The .zip file (http://www.netbeans.org/files/documents/4/569/profilertutorial.zip) for that tutorial contains two projects: exercise1 and exercise2. The exercise1 project appears to be okay - the Profiler still works with it. But when exercise2 is the main project the Profiler's "Profile Main Project" menu entry is disabled. The "Profile Project" context menu entry is also disabled. So something has changed when using the Profiler with the latest Q build. The exercise2 project works fine with NB 5.0 Beta with Milestone9 on the same system (if it didn't, we wouldn't have a Profiler tutorial available :-) ). If there is something we need to change in the exercise2 project, please let us know ASAP. As it is right now, the tutorial won't work with the latest Q build.
Profiler M9 was tested and released for NetBeans 5.0beta. Since that some NetBeans API changes were made so the M9 won't work correctly with newest daily- and Q-builds. As for this particular case, the exercise2 is a webproject which can't be profiled in NB after 5.0beta. The reason is that versions of some NB modules related to webprojects were changed, which disabled webprojects support in Profiler. There are some other problems using M9 with newest NB builds, for example configuring Profiler settings in NB Options panel won't work. Note that all these problems are related to NB API changes and cannot be fixed by modifying projects. To be able to successfuly use the tutorial with Profiler M9, the user has to use NetBeans 5.0 beta. Internally, to be able to use newest NetBeans builds, you have to use latest Profiler builds.
Verification of old issues.
Closing old issues
Reverting to original Target Milestone value changed by mistake. Sorry for inconvenience.