You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2019/07/30 09:55:00 UTC

[jira] [Closed] (MNG-6725) Skip '.mavenrc' via MAVEN_SKIP_RC=1 and '-Dmaven.skip.rc=true' on child ITs (by default on Jenkins CI).

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

Tibor Digana closed MNG-6725.
-----------------------------
       Resolution: Done
    Fix Version/s: 3.6.x-candidate

> Skip '.mavenrc' via MAVEN_SKIP_RC=1 and '-Dmaven.skip.rc=true' on child ITs (by default on Jenkins CI).
> -------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6725
>                 URL: https://issues.apache.org/jira/browse/MNG-6725
>             Project: Maven
>          Issue Type: Task
>          Components: Integration Tests
>    Affects Versions: 3.6.x-candidate
>         Environment: ASF Jenkins CI
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.6.x-candidate
>
>
> This is related to the problem with MAVEN_OPTS.
> If Jenkins has global '.mavenrc' then the environment variables are merged with local ones and applied in Maven JVM which is controlled by $MVN_HOME/bin/mvn
> If you want to isolate the JVM from global '.mavenrc', you have to set environment variable to non-zero length value, i.e. MAVEN_SKIP_RC=1.
> This commit controls skipping '.mavenrc' in {{AbstractMavenIntegrationTestCase}}.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)