Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: maven-invoker-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 1.642.1
      Maven 3.3.9
      Maven Plugin 2.7.1
    • Similar Issues:

      Description

      Maven 3.3+ supports maven.config files in the .mvn folder of a maven project. This file provides support for providing system properties to the JVM at build time. Running Maven builds in Jenkins is doing something to prevent this file from being picked up. Running in Hudson or from the command line on the Jenkins slave works correctly. Running from Jenkins does not.

      An example is attached. maven.config should be in .mvn folder at the root of the project.

      Incorrect output from Jenkins
      [INFO] — exec-maven-plugin:1.4.0:exec (parmValue) @ jenkins-maven-config —
      ERROR: Not Set

      Correct output should be:
      [INFO] — exec-maven-plugin:1.4.0:exec (parmValue) @ jenkins-maven-config —
      HelloWorld

        Attachments

        1. maven.config
          0.0 kB
        2. pom.xml
          1 kB

          Issue Links

            Activity

            Hide
            aheritier Arnaud Héritier added a comment -

            This was a bug in maven (https://issues.apache.org/jira/browse/MNG-5889) which was making .mvn folders not usable with -f option. It is fixed in 3.5.x

            Show
            aheritier Arnaud Héritier added a comment - This was a bug in maven ( https://issues.apache.org/jira/browse/MNG-5889)  which was making .mvn folders not usable with -f option. It is fixed in 3.5.x

              People

              • Assignee:
                olamy Olivier Lamy
                Reporter:
                p51asp Derek Sharpe
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: