[
https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10715:
-------------------------------------
Daniel:
When launching JBoss, none of the .sh or .bat scripts are being accessed, so any
customizations to the PATH you've made will not be represented inside eclipse. All
servers will need "native" on their path. Other customizations can be made by
the user as they wish. Since, when creating the server, we have no way to know what other
path additions you would like to make, we helpfully begin by adding native. I've also
jsut checked, and any additions you make will be persisted properly.
Is our structure interfering with your ability to edit the path in any way? How were you
previously setting the path, if not via the launch configuration? Since your
customizations are persisted, what exactly can we do better for this situation, such that
the majority of users have 'native' automatically added, but those who require
further customizations can make them?
Thanks in advance
"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
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