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.
|Summary:||[Exec/Compile] Add support for setting vmargs on a class basis|
|Product:||java||Reporter:||Scott Stark <starksm>|
|Component:||Project||Assignee:||Jesse Glick <jglick>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
|Bug Depends on:||17826|
Description Scott Stark 2000-12-08 21:42:02 UTC
When testing certain types of development(security, JAAS, JSSE) one needs to specify additional vmargs to control the behavior of the mv(-Djava.security.manager, -Djava.security.policy, -Djava.security.auth.login.config, ...) It would be nice if there was a VM Arguments property in the Exceution tab of a main class to facilitate the setting of these value. Currently I have to define a new external execution type with these values.
Comment 1 Svata Dedic 2001-01-17 09:33:59 UTC
Hmm, it seems (for me) that new execution type is the right thing you should do here - you ARE define a new execution environment. It can be then used by this class, or by any other class that you want to share execution properties with. Can you explain why this style does not fit you ?
Comment 2 Scott Stark 2001-01-17 17:31:59 UTC
When I'm setting vm parameters I find these to be more a function of the class I'm running rather than a particular usage of a given vm. That is why I would like to be able to set these as a property of the class in its Execution settings rather than doing this by setting up/changing the Executor settings.
Comment 3 Svata Dedic 2001-01-17 17:35:59 UTC
What about composing the settings for a class to be run and general properties found in the Executor ?
Comment 4 Scott Stark 2001-01-17 17:48:59 UTC
I can do that. It requires bringing up the Executor dialog, selecting the Expert tab, and then seleting the Environment Variables to be able to set the value. My two issues with this are: 1. This is more tedious than just being able to set the vm args via a "VM Arguments" in the class Exceution properties. 2. The vm arguments are more a function of the class than the vm/executor. Setting the security policy file is one example.
Comment 5 Svata Dedic 2001-01-17 17:53:59 UTC
Sorry, I didn't express myself clearly. I meant what if I provide "VM arguments" property on class' property sheet besides the current "Arguments" one and add the class-specific settings after those provided by the configured Executor. This way, you (or other users) will be in charge to decide whether the parameter is VM- or environment- specific, or task-/class- specific. Does it sound reasonable ?
Comment 6 Scott Stark 2001-01-17 17:57:59 UTC
That sounds perfect.
Comment 7 Martin Matula 2004-11-13 23:47:02 UTC
Comment 8 Jesse Glick 2004-12-01 19:36:51 UTC
*** This issue has been marked as a duplicate of 49636 ***
Comment 9 Jesse Glick 2004-12-01 19:37:47 UTC
Note in 4.0 you can set per-project VM arguments in the project properties dialog.