[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Daniel Atallah commented on JBIDE-10715: ---------------------------------------- Thanks for the clarification, I was thinking that it was actually unintentional the Path was being set to "native", but I now see that it isn't. I realize that none of the startup scripts are being used. I'm actually referring to the current System Path (which, since I'm on Windows, this becomes part of java.library.path), not anything that is overridden for JBoss specifically at all in a startup script or etc. The reason I want this is because I'm using a database driver that needs a native library in java.library.path (Oracle OCI). I realize that I could manually add any required paths to the launch config., but it seems to be that step should be unnecessary since it's all already in my system Path. Would it not make more sense make the default Launch Configuration work more similarly to the run.bat where, instead of overriding the Path environment variable, "bin/native" is appended to it? (Something like "native;${env_var:Path}" I think it'd also be more clear what the intent of the "native" value is if the full Path was specified more explicitly, e.g. "${jboss_home}/bin/native;${env_var:Path}" Hopefully this clarifies the situation. -- 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

[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10715: --------------------------------------------- Rob - looking at how AS 5 itself sets the path with respect to native then that is just passed in via -Djava.library.path Why are we doing this via the global environment settings ? -- 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

[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10715: ------------------------------------- The patch was contributed via a user here: https://issues.jboss.org/browse/JBIDE-2735 -- 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

[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Daniel Atallah commented on JBIDE-10715: ---------------------------------------- The "Append environment to native environment" vs. "Replace native environment with specified environment" radio buttons refer to the entire environment, not to specific individual environment variables. * With "Append...", any environment variables specified in the launch config will be appended to the set of environment variables inherited from the Eclipse process and given to the JBoss process. ** If a variable is explicitly specified in the launch configuration, it will override any inherited variable of the same name * With "Replace...", the only environment variables given to the JBoss process with be the ones explicitly specified in the launch configuration - none are inherited You can see the effect on the Path (that is is overridden instead of appended to) by looking at "java.library.path" in the output of "showAll" in the "SystemProperties" MBean, but this doesn't give the full picture because other stuff messes with java.library.path and you don't see the rest of the environment variables. I didn't see an easy way to dump the environment contents via the JMX console, but putting the following snippet in a JSP will do the trick: {code} <% for (java.util.Map.Entry<String,String> env : System.getenv().entrySet()) { System.out.format("%s=%s\n", env.getKey(), env.getValue()); } %> {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Daniel Atallah commented on JBIDE-10715: ---------------------------------------- In the commit for this (https://source.jboss.org/changelog/JBossTools?cs=38738) the path separator is hard-coded to ":" - this won't work on Windows. It needs to somehow use {{System.getProperty("path.separator")}}. On Windows, environment variable names are case-insensitive, so it did somewhat work on Windows with the variable spelled badly. -- 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

[ https://issues.jboss.org/browse/JBIDE-10715?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-10715. ------------------------------- Verified with jbdevstudio-product-linux-gtk-5.0.0.v201204301418M-H119-Beta3. -- 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