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.
In project.properties I have: javac.compilerargs=-Xbootclasspath/p:${build.classes.dir} run.jvmargs=-Xbootclasspath/p:${build.classes.dir} ... but in project properties window I see: Additional Compiler Options: -Xbootclasspath/p:build/classes VM Options: -Xbootclasspath/p:${build.classes.dir}
I use NB 6.0 M10
Obviously some variables are interpreted and some are not. Reassigning to java for evaluation (I hope it's the right component).
Both should be evaluated.
The problem is in J2SEProjectProperties.readRunConfigs which does not evaluate the properties, I am not sure if it's save to use the project's property evaluator to evaluate the value (the run configurations may override the value of referenced property). Jesse, is it save to do evaluator.evaluate(property) on the properties read from the configurations?
No, it is not safe to use the evaluator in this context. I don't see an obvious fix for this, but it seems mostly harmless. The Properties dialog is anyway not safe to use when you have made special customizations such as this in project.properties.
OK, I agree that it not P3. Thanks for help.
Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next".
Editing those fields corrupts current project.properties without warning. IMHO it's time to repair this. Suggestion: Don't display interpreted variables in project properties window, so user would be aware of possible problems if editing those fields.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss