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.
Using variables as it common in OpenOffice.org works with NB 5.0 but no longer in 6.x This was really usable feature often used by Sun's developer here in Hamburg ;-) file.reference.unoil.jar=${Env-SOLARVER}\\${Env-OUTPATH}\\bin${Env-UPDMINOREXT}\\unoil.jar file.reference.java_uno.jar=${Env-SOLARVER}\\${Env-OUTPATH}\\bin${Env-UPDMINOREXT}\\java_uno.jar file.reference.ridl.jar=${Env-SOLARVER}\\${Env-OUTPATH}\\bin${Env-UPDMINOREXT}\\ridl.jar file.reference.juh.jar=${Env-SOLARVER}\\${Env-OUTPATH}\\bin${Env-UPDMINOREXT}\\juh.jar file.reference.jurt.jar=${Env-SOLARVER}\\${Env-OUTPATH}\\bin${Env-UPDMINOREXT}\\jurt.jar Building the sources still works when adding <target name="-pre-init"> <property environment="env."/> <tempfile property="env.properties" prefix="env" suffix=".properties"/> <echoproperties destfile="${env.properties}"> <propertyset> <propertyref prefix="env."/> <mapper type="glob" from="env.*" to="Env-*"/> </propertyset> </echoproperties> <property file="${env.properties}"/> <delete file="${env.properties}"/> </target> to the build.xml but the ide still shows unresolved jars. I'll set this to P2 because it's a regression.
Reassigning to "projects" for evaluation.
issue 136516 should solve this in a generic manner maybe? marking as duplicate *** This issue has been marked as a duplicate of 136516 ***
This one is not fixed with the variables dialog. It is not possible to access variable set by the environment of the shell starting netbeans. To reproduce: bash export MY_CHILD_WORK_SPACE=dba32e netbeans & => access the variable in the projects.properties file like file.reference.source= /cws/${Env-MY_CHILD_WORK_SPACE}/dbaccess/qa
Don't think this behavior was ever documented/guaranteed, but could be useful. No idea if such functionality was ever intentionally removed (or added for that matter). Handled by j2seproject, not infrastructure.