[
https://issues.apache.org/jira/browse/MNG-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896063#comment-16896063
]
Hervé Boutemy commented on MNG-6725:
------------------------------------
why create a separate issue from MNG-6714?
and why not simply let INFRA fix .mavenrc script: the script should be fixed
if INFRA does not want to fix the script, sure, we can workaround with
MAVEN_SKIP_RC env variable, but really this should bot be useful to fight
against infra
(and I don't know what maven.skip.rc Java system property means)
> 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
> 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)
