You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/10/03 17:55:00 UTC
[jira] [Updated] (MSHARED-1141) ForkedLauncher#run() uses a misconception of JAVA_HOME
[ https://issues.apache.org/jira/browse/MSHARED-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MSHARED-1141:
------------------------------------
Fix Version/s: maven-verifier-next
> ForkedLauncher#run() uses a misconception of JAVA_HOME
> ------------------------------------------------------
>
> Key: MSHARED-1141
> URL: https://issues.apache.org/jira/browse/MSHARED-1141
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-verifier
> Reporter: Michael Osipov
> Priority: Major
> Fix For: maven-verifier-next
>
>
> The code does:
> {noformat}
> if ( envVars == null || envVars.get( "JAVA_HOME" ) == null )
> {
> cmd.addEnvironment( "JAVA_HOME", System.getProperty( "java.home" ) );
> } {noformat}
> This is logically wrong because {{java.home}} is not {{{}JAVA_HOME{}}}. {{java.home}} points to the JRE directory which can or cannot be the {{{}JAVA_HOME{}}}. This block can be removed all together and shall be eiher inherited or provided by the client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)