[
https://issues.apache.org/jira/browse/KARAF-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748821#comment-16748821
]
ASF subversion and git services commented on KARAF-6108:
--------------------------------------------------------
Commit c2378f0afa9b887be6dc863ea913cfbfb077d42d in karaf's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=c2378f0 ]
Merge pull request #736 from jbonofre/KARAF-6108
[KARAF-6108] Include JAVA_HOME/bin in wrapper default PATH
> Service wrapper should add selected JAVA_HOME also to the PATH variable.
> ------------------------------------------------------------------------
>
> Key: KARAF-6108
> URL: https://issues.apache.org/jira/browse/KARAF-6108
> Project: Karaf
> Issue Type: Improvement
> Components: karaf
> Affects Versions: 4.1.6
> Reporter: Jürgen Kindler
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.1.8, 4.2.3
>
>
> When running applications in Karaf that spawn Java processes, the currently
> used path to find Java is not necessarily available in the context of Karaf.
> Karaf itself will be started fine, but when attempting to spawn a child
> process, the Java executable may not be found unless the system user's
> context has explicitly configured the path in $PATH.
> In order to be sure that all possible child processes have access to the same
> Java that also runs Karaf, I suggest to add 2 lines to the wrapper templates
> ( karaf-wrapper-java*.conf )
> {code:java}
> set.default.PATH_WITH_JAVA=%JAVA_HOME%%WRAPPER_FILE_SEPARATOR%bin%WRAPPER_PATH_SEPARATOR%%PATH%.
> set.PATH=%PATH_WITH_JAVA%{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
