You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/04/05 13:12:00 UTC
[jira] [Updated] (MNG-7141) different environment variables like
JAVA_HOME depending on the project.
[ https://issues.apache.org/jira/browse/MNG-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MNG-7141:
--------------------------------
Component/s: maven wrapper
> different environment variables like JAVA_HOME depending on the project.
> ------------------------------------------------------------------------
>
> Key: MNG-7141
> URL: https://issues.apache.org/jira/browse/MNG-7141
> Project: Maven
> Issue Type: Improvement
> Components: maven wrapper
> Reporter: Terrien Jean-Yves
> Priority: Major
>
> Hello,
> A suggestion :
> Add in script just after
> {code:sh}
> if [-f "$ HOME/.mavenrc"]; then
> . "$ HOME/.mavenrc"
> fi
> # <==== this to load local mavenrc
> if [-f ".mvn/mavenrc"]; then
> . ".mvn/mavenrc"
> fi
> {code}
> This allows to have different environment variables like JAVA_HOME depending on the project.
> Currently it is possible to choose the version of maven in the properties file but not the version of java.
> In all projects, the maven command is run with the same version of java because it depends on the user's environment and not the project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)