You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2020/10/21 03:14:00 UTC
[jira] [Resolved] (SLING-9843) fallback to java.home system
property if JAVA_HOME env variable is not set
[ https://issues.apache.org/jira/browse/SLING-9843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-9843.
--------------------------------
Resolution: Fixed
Fixed at: https://github.com/apache/sling-feature-launcher-maven-plugin/commit/8e639d8b29fe0956bf9e0d3d4599cef3b80893d4
> fallback to java.home system property if JAVA_HOME env variable is not set
> --------------------------------------------------------------------------
>
> Key: SLING-9843
> URL: https://issues.apache.org/jira/browse/SLING-9843
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.2
>
>
> If JAVA_HOME env variable is not set, then the launcher fails as it tries to run with this error:
> {code:java}
> Cannot run program "null/bin/java" error.{code}
> Falling back to the java.home system property would also get us the path to the java jre that should work for launching the java process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)