Closed brianoliver closed 10 years ago
@brianoliver said: Accidentally closed!
@brianoliver said: There seems to be a few different scenarios here.
Start with the Environment Variables defined by the Running Java Application (currently called "inherit"). (perhaps "EnvironmentVariables.startingWith(LocalPlatformDefaults)" instead?)
Start with a clean environment (currently called "empty"). (perhaps "EnvironmentVariables.startingWith(CleanEnvironment)" instead?)
Start with what ever environment variables are declared on the target platform (may not always be possible). (perhaps "EnvironmentVariables.startingWith(TargetPlatformDefaults)" instead?)
@brianoliver said: Note: We did not implement the ability to "unset" a property as this is not achieve able across platforms. However setting a property to "" may achieve the same outcome.
This issue was imported from JIRA ORACLETOOLS-152
Reported by @brianoliver
Marked as fixed by @brianoliver on Monday, September 8th 2014, 5:14:45 pm
As discussed with our QA team, it would be great if they could inherit and then unset specific environment variables.