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.
Profiler 070420 NetBeans IDE Dev (Build 070423) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Steps to reproduce: - Make sure that <Use Java Platform Defined In Project> is selected in Profiler Options. - Right-click JBoss server in Runtime view and select Start in Profile Mode - or - Right-click any project targeted to JBoss server - RESULT: Select Java Platform for Profiling dialog is shown even JDK platfrom in JBoss server Customizer is already selected
Not a problem in Profiler, just current state of JBoss serverplugin implementation, nothing can be done on Profiler side. Feel free to file a RFE for JBoss serverplugin.
Currently profiler is not able to determine JDK platform for JBoss projects. So I reopen the issue. I believe you need to file the issues against non-working API that you use. After that, you could add the dependency between the issues.
Profiler is not able to determine JDK platform set for JBoss server because JBoss serverplugin doesn't provide this information. Also note that Profiler isn't able to detect current outside temperature from profiled JVM because the JVM doesn't provide this information. Feel free to file a RFE for JBoss serverplugin. If you want, you can also file a RFE to JVM... Note that I don't have any problem with current state from Profiler point of view - profiling works and server is started with correct JDK selected by the user. Moreover, Profiler uses all available APIs correctly. If you are unsatisfied, it's absolutely OK but then you should file a RFE to JBoss serverplugin and don't force Profiler developers to do it by creating bugs in Profiler. HINT: Reopen this issue, change it from DEFECT to ENHANCEMENT and assign it to JBoss serverplugin.
Verified Filed Issue 103483 for JBoss plugin