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 2021/03/14 16:16:00 UTC

[jira] [Commented] (MWRAPPER-12) different environment variables like JAVA_HOME depending on the project.

    [ https://issues.apache.org/jira/browse/MWRAPPER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301186#comment-17301186 ] 

Michael Osipov commented on MWRAPPER-12:
----------------------------------------

Is this really portable across user/CI installations?

> different environment variables like JAVA_HOME depending on the project.
> ------------------------------------------------------------------------
>
>                 Key: MWRAPPER-12
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-12
>             Project: Maven Wrapper
>          Issue Type: Improvement
>            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)