[
https://issues.apache.org/jira/browse/MNG-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896041#comment-16896041
]
Tibor Digana commented on MNG-6726:
-----------------------------------
See the branch MNG-6726 in maven and maven-integration-testing:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=ad58ca489038829d5c9d54d7201ddf3eac49ad20
https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=f838934c0a1a670c012bd669f8766efa6b6e8320
> 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
> Priority: Major
> 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)
