[
https://issues.apache.org/jira/browse/KARAF-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172971#comment-13172971
]
Andreas Pieber commented on KARAF-1116:
---------------------------------------
OK, the problem is not what you do it self, but rather that the Karaf scripts
define %JAVA% as the executable. Since you define JAVA as the path to
%JAVA_HOME%\bin this (logically with this additional information) fails. Well,
we've the following possibilities now:
# close this as wont fix and assume that ppl dont define JAVA as
%JAVA_HOME%\bin or something else ambitious
# probe if %JAVA% is an executable and otherwise go the "regular way" using
$JAVA_HOME%\bin\java
TBH I'm a little bit in favor of option 1; but I'm open for other opinions :-)
> Scripts fail at resolving java jdk.
> ------------------------------------
>
> Key: KARAF-1116
> URL: https://issues.apache.org/jira/browse/KARAF-1116
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 2.2.4
> Environment: Windows 7 x64
> Reporter: Lukas Stampf
> Assignee: Andreas Pieber
> Fix For: 2.2.5, 3.0.0
>
>
> Scripts like karaf.bat have a problem resolving the java jdk under windows,
> when the variables are setup this way:
> JAVA_HOME = F:\Java\jdk
> JAVA = %JAVA_HOME%\bin
> Path = various stuff; %JAVA%
> echo %PATH%
> results in the correct output of: F:\Java\jdk\bin
> If the JAVA variable is deleted and the Path is set to %JAVA_HOME%\bin it
> does work, although the resulting path is the same.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
