]
Andrej Podhradsky edited comment on JBDS-3345 at 4/23/15 4:14 AM:
------------------------------------------------------------------
Note that the above script works perfectly only if we add the following to the top of the
script (on unix-based system)
{code}
export PATH=/opt/java/jdk1.7.0_75/bin:$PATH
{code}
It seems that the server somewhere calls {{java ...}} so the JDK is taken from {{PATH}}.
So, my question is: Should JBDS set the PATH with the appropriate JDK for the whole
execution?
was (Author: apodhrad):
Note that the above script works perfectly only if we add the following to the top of the
script (on unix-based system)
{code}
export PATH=/opt/java/jdk1.7.0_75/bin:$PATH
{code}
It seems that the server somewhere calls [[java ...]] so the JDK is taken from [[PATH]].
So, my question is: Should JBDS set the PATH with the appropriate JDK for the whole
execution?
Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
-----------------------------------------------------------------
Key: JBDS-3345
URL:
https://issues.jboss.org/browse/JBDS-3345
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: server
Affects Versions: 8.0.2.GA
Environment: Fedora 21 x86_64
JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
Reporter: Andrej Podhradsky
Priority: Critical
Attachments: compiler.png, console.png, errors.txt, error_log.txt,
installed_jre.png, runtime_jre.png, server.log
FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8
we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors
in the attached file.
Moreover, we are not able to stop the server from IDE, the process is still alive and we
have to kill it manually.
Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with
jdk 7 the server works fine.