You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/09/15 11:43:00 UTC

[jira] [Updated] (SLING-7128) slingstart-maven-plugin should respect JAVA_HOME when set

     [ https://issues.apache.org/jira/browse/SLING-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-7128:
-----------------------------------
    Fix Version/s:     (was: Slingstart Maven Plugin 1.7.8)
                   Slingstart Maven Plugin 1.7.10

> slingstart-maven-plugin should respect JAVA_HOME when set
> ---------------------------------------------------------
>
>                 Key: SLING-7128
>                 URL: https://issues.apache.org/jira/browse/SLING-7128
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Slingstart Maven Plugin 1.7.10
>
>
> The typical way of configuring a different Java binary to use is by setting the JAVA_HOME environment variable. This allows for instance using a different JVM version than the default one.
> The slingstart-maven-plugin ( in LauncherCallable ) unconditionally uses 'java' as the command name. We should allow for a custom JAVA_HOME to be set.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)