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 run.jvmargs are not taken from the current run configuration like the application arguments are. I realize that the VM args that may be used for profiling may be different than normal ones, but not necessarily. I am currently using some jvmargs to configure my application when in a test environment. This does not work with profiling. I saw the advanced options for profiling, but these seem more for altering the profiling than for passing run configurations. It looks like this would be a build unwieldy for this purpose. If I alter the profile macro, create a new property <property name="foo" value = "${profiler.info.jvmargs} ${run.jvmargs}"/> And then, change <jvmarg line="${profiler.info.jvmargs}"/> to <jvmarg line="${foo}"/> It seems to work. However, if the properties in the run configuration are in the form run.jvmargs = -Daaa=bbb \ -Dccc=ddd It does not work. If the '\' is removed and everything is on one line, it does work.
Reassigning to "profiler" for evaluation...
profiler has been fixed to work correctly with the run configurations
I tried to test this with the daily build 200708280000 and it still does not work for me. Is this fix publicly available yet? Or perhaps I need to reset my project somehow?
please, try build 200708290000 - in that build the fix works. Eg. I created new configuration with different -Xmx settings and after running jps -v I can see the settings from the configuration are used.
That build is not available yet on the website. However, I will get it as soon as it is and verify the fix. Thanks.
Seems to work with my run configurations!