[jbosstools-issues] [JBoss JIRA] (JBIDE-10715) "Path" Environment Variable in Launch Configuration is overridden with the text "native" by default
[
https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-10715.
---------------------------------
Resolution: Done
Somewhat ridiculously, my test here shows the Path is not even being properly passed in to
the launch, since the current codebase uses Path instead of PATH. Apparently this
case-sensitive situation means that the environment variable is 100% useless and is not
even functioning as it should. That's what I get for not fully testing a
user-contributed patch I guess.
Other tests do show that native:${env_var:PATH} work as suggested, and so I'll commit
that right now.
"Path" Environment Variable in Launch Configuration is
overridden with the text "native" by default
---------------------------------------------------------------------------------------------------
Key: JBIDE-10715
URL: https://issues.jboss.org/browse/JBIDE-10715
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows 7 / Eclipse Indigo SR1 / JBoss 4.2.3
Reporter: Daniel Atallah
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
Attachments: JBIDE-10715.png
When a new Launch configuration is created for a JBoss 4.2 Runtime server, the
"Environment" tab contains an initial entry for the "Path" variable
with a value of "native".
This causes the Path of the launched process to be overridden and subsequently not work
correctly if you depend on the System Path for anything.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira