[ https://issues.jboss.org/browse/JBIDE-12229?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12229: ------------------------------------- I'm pretty confused, since I just started it with a jre and the -server argument, and got no errors. I did not see any copy of the errors on JBIDE-12227 mentioning a server folder not found. -- 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-12229?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12229: ------------------------------------- Committed to maintenance. -- 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-12229?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-12229: ------------------------------------------- Rob, Martin, do you think this is windows specific problem? I've just tried to run EAP 6 with JRE and, as Rob, I got no errors, so I don't know how to verify error message when I am getting no error :) -- 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-12229?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12229: --------------------------------------- Jaro, yes, this was a Windows-specific problem I believe. I had this problem with 5.0.0. So if you don't see the problem anyway, it's because Rob fixed it, no? :) -- 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-12229?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-12229: ------------------------------------------- Martin, I believe the problem here was that error message is not obvious, not fixing the error. Or am I missing something? -- 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-12229?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12229: --------------------------------------- There has been a similar problem discussed in the forum: https://community.jboss.org/thread/171560 -- 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-12229?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12229: ------------------------------------- I just made a commit. It seems on linux, jre's under 1.7.x were NEVER Returning -server anymore. This was clearly a bug. However I am NOT able to replicate at all where a server adds the -server flag and shouldn't. On windows, for ALL versions of java, the location of the 'server' folder is ${jdkhome}\jre\bin\server This has not changed through any versions of java at all. The code in JavaUtils clearly recognizes this fact: {code} private static File getWindowsServerLibFolder(String version, IVMInstall install) { IPath locPath = new Path(install.getInstallLocation().getAbsolutePath()); return locPath.append("jre").append("bin").append("server").toFile(); //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ } {code} Are you sure you're using a clean workspace with all new servers? This will not update old servers, but will only affect the server on creation. -- 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-12229?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12229: --------------------------------------- Ok, you're right, it works in new workspace and new servers. However, if you change the JRE of the runtime for a given server later no change will happen. Could that be fixed as well? When you're in the server editor, open the runtime environment settings and change the name the server editor will reflect the change. This could work similarly when you change the JRE to one that conitains/does not contain the server folder so the parameter could be added/removed. -- 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-12229?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12229: -------------------------------- Attachment: JBIDE-12229.v5.patch new patch -- 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-12229?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-12229. --------------------------------- Resolution: Done committed trunk and maintenance -- 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-12229?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12229: -------------------------------- Fix Version/s: 4.0.x (was: 3.3.2) (was: 4.0.0.Alpha2) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12229?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12229: -------------------------------- Attachment: patch.txt here's a patch for it. The issue might be due to jre and jdk having an extra folder in the path. THat's how I replicated in windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12229?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12229. --------------------------------- The -server parameter is added at the end which I quite don't like as much but it works ;) So finally I'm closing this JIRA - it is fixed. Verified in JBDS 6.0.0.CR1 B111. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira