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.
[ BUILD # : 200509151800 ] [ JDK VERSION : 1.5.0_02 ] In Module Suite Project you can't the VM Options and Arguments in the Project Properties Dialog. So things like "-J-Xms24m -J- Xmx64m" must be edit in etc/feedreader.conf as example. And evertime you generate the project you must edit it again. Here i think is caution needed. Form a Module Suite Project are not only ZIP Application generated. Also JNLP can be generated. And by JNLP not all VM Options can use: http://java.sun.com/j2se/1.5.0/ docs/guide/javaws/developersguide/syntax.html#resources
Not in 5.0.
Not implemented in time for 5.0u1, sorry.
Should work set to set in suite project.properties e.g. run.args.extra=-J-Dfoo=bar -J-Xmx256m
Is this issue for etc/myapp.conf file in the build-zip, or for the 'run' ant target, or both?
Probably just for the 'run' Ant target. Of course the build harness could append those args to the app.conf file when building a ZIP, but I wouldn't want to hazard a guess as to what fraction of the time this would be correct! If you have special needs for your app's launcher you are as always advised to write your own target to build it, using the harness' default target as a starting point.
*** Issue 96522 has been marked as a duplicate of this issue. ***
*** Issue 110036 has been marked as a duplicate of this issue. ***
After feature freeze.
This has come up on the mailing list a few times recently. Although one could manually add a target to replace or update the .conf file to use a similar setting in the ZIP distribution, each developer must reinvent the target to do the same thing. I agree it would be a very nice feature to have in the IDE. If implemented and the tools support does not also update the run.args.extra property in the suite, then at least the help page should mention that this setting is for ZIP distributions only and does not affect when run from the IDE.
Seems there needs to be another value along with run.args.extra something like run.args.extra.perm which gets propagated to the final build. Then run.args.extra and run.args.extra.perm can be merged, and that can allow folks to have some options specific to development. It would be best to use run.args.dev and run.args.perm/prod or something, but .extra is already in use with the scenario it supports, and that scenario still exists; there are some options one would just want to use at development time instead of production, and of course there are options one wants set in the file at deployment of the application. For instance, a non-visual application will always want to have the splash screen turned off. Applications which do not allow their users to add other modules will most likely want a specific min and max memory for the application to make it work best for what it does. So, I strongly believe there needs to be two concepts supported by two variables.
Too, both options should be supported in the suites UI.
In harness/jnlp.xml I found that "run.args" is used for the "run-jnlp" (suite.xml)/ "run" (jnlp.xml) target. Unfortunatly, I couldn't find any documentation about it, and it isn't used in the "build-jnlp" target either, so it doesn't make it into master.jnlp.
I filed the following issue: http://www.netbeans.org/issues/show_bug.cgi?id=158098 which is related to this one.
"So things like "-J-Xms24m -J-Xmx64m" must be edit in etc/feedreader.conf as example. And evertime you generate the project you must edit it again" - this is horrible and I needed to solve it as part of bug #179388 too. I've introduced new property app.conf which (if set to feedreader.conf) would allow one to provide completely own version of the config file in ${suiter.dir}/feedreader.conf.
*** Bug 182247 has been marked as a duplicate of this bug. ***