maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MNG-6726) Integration tests should use non empty MAVEN_OPTS. Jenkinsfile and 'core-it-suite' should accept custom MAVEN_OPTS from developers and their CLI.
Date Tue, 30 Jul 2019 10:58:00 GMT
Tibor Digana created MNG-6726:
---------------------------------

             Summary: Integration tests should use non empty MAVEN_OPTS. Jenkinsfile and 'core-it-suite'
should accept custom MAVEN_OPTS from developers and their CLI.
                 Key: MNG-6726
                 URL: https://issues.apache.org/jira/browse/MNG-6726
             Project: Maven
          Issue Type: Task
          Components: Integration Tests
         Environment: Jenkins CI, development environment too
            Reporter: Tibor Digana
            Assignee: Tibor Digana
             Fix For: 3.6.x-candidate


Using non-empty {{MAVEN_OPTS}} (dummy prop) to prevent from merging env vars in child integration
test with env vars from (caller) parent process.

The child env var takes the precedence in this fix.
Merging env vars between parent/child processes is performed in maven-shared-utils:
see {{Commandline#addSystemEnvironment()}} and see the line
{{Properties systemEnvVars = CommandLineUtils.getSystemEnvVars()}}.

With this fix we can freely use the {{MAVEN_OPTS}} within our integration tests.



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

Mime
View raw message