Uploaded image for project: 'Maven'
  1. Maven
  2. 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.

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: In Progress
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.6.x-candidate
    • Component/s: Integration Tests
    • Labels:
      None
    • Environment:
      Jenkins CI, development environment too

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tibordigana Tibor Digana
                Reporter:
                tibordigana Tibor Digana
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: