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.

Bug 12652 - Allow system properties to be set for individual executable java files
Summary: Allow system properties to be set for individual executable java files
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker with 4 votes (vote)
Assignee: issues@java
URL:
Keywords:
: 27719 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-06-08 00:40 UTC by jsisson
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jsisson 2001-06-08 00:40:06 UTC
Currently netbeans allows you to set arguments for a class in the execution 
tab of the class's property sheet, but it does not allow you to 
specify system properties that are to be passed to the class.

Considering that in the Java tutorial, it is recommended that system properties 
be used rather than command line arguments for passing information to a 
program, this enhancement request should be seriously considered.  See:
 
 http://java.sun.com/docs/books/tutorial/essential/attributes/cmdLineArgs.html

The only way you can set system properties in netbeans 3.2 is by cloning an 
executor and adding the "-Dproperty=value" settings in the executors process 
aguments property.

I would like to be able to configure properties on a per class basis.

I have some suggestions:

* Add a "System property tag replace" property (with a default value of "-D" ) 
on the appropriate executor, debugger and compiler types on the expert tab 
(just like there are tag replacement properties on the expert tab of some of 
the compiler types).  The reason I suggest this is that there are some VMs that 
do not use the -D tag for passing system properties (e.g. The Microsoft VM has 
the format "/d:<name>=<value>").

* Add a {systemproperties} tag that can be substituted into the process 
arguments when executing the VM (e.g. like {bootclasspath} ).

* Add a "System properties" property to the execution tab on the properties 
panel for an executable java file (so now there will be both an 'Arguments' 
and 'System properties' properties on the properties panel).
Comment 1 Jan Zajicek 2001-06-08 12:41:50 UTC
I am not sure who should handle this, may be it will be necessary handle it in
java module, it will be java file property like Arguments.
Comment 2 Jan Chalupa 2001-11-27 11:53:43 UTC
Target milestone -> 3.3.1.
Comment 3 Jan Chalupa 2001-11-27 11:57:12 UTC
Target milestone -> 3.3.1.
Comment 4 Jan Chalupa 2002-01-11 14:04:57 UTC
Target milestone -> 3.4
Comment 5 Jan Chalupa 2002-01-11 14:08:39 UTC
Target milestone -> 3.4
Comment 6 Jan Chalupa 2002-01-11 14:09:29 UTC
Target milestone -> 3.4
Comment 7 Jan Chalupa 2002-01-11 14:12:03 UTC
Target milestone -> 3.4
Comment 8 Marek Grummich 2002-07-22 08:41:11 UTC
Target milestone was changed from '3.4' to TBD.
Comment 9 Marek Grummich 2002-07-22 09:04:00 UTC
Target milestone was changed from '3.4' to TBD.
Comment 10 Jesse Glick 2002-07-23 03:22:16 UTC
Java module's business.
Comment 11 Jan Becicka 2002-08-06 11:10:39 UTC
New projects infrastructure could solve it, 
isn't?
Comment 12 Jesse Glick 2003-04-24 15:06:07 UTC
*** Issue 27719 has been marked as a duplicate of this issue. ***
Comment 13 Jesse Glick 2003-04-24 15:06:42 UTC
See also issue #17980.
Comment 14 Jan Pokorsky 2003-11-27 14:36:40 UTC
Removed PROJECTS keyword since the projects prototype has been
canceled. For more details see
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss
Comment 15 psuk 2004-07-15 14:05:48 UTC
Execution properties were removed with new ant-based build system and
replaced by readable project.properties in nbproject directory.

You can specify application arguments (application.args) and JVM
arguments (run.jvmargs).