Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25760

Jenkins maven-plugin cannot deal with mavens advanced reactor options

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Jenkins v1.565.3, Maven-Plugin version 2.7

      The Jenkins Maven Plugin cannot deal with the advanced reactor options of Maven.
      See http://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options

      When e.g. executing a a maven build with the following maven command in Jenkins:
      mvn clean install -pl !excludedModule

      one gets the following error:

      Executing Maven:  -B -f /myworkspace/myproject/pom.xml clean install -pl !excludedModule
      [INFO] Scanning for projects...
      [ERROR] Could not find the selected project in the reactor: !excludedModule -> [Help 1]
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
      channel stopped
      

      Running the same command on the same project with the same maven version on the command line it works fine.

      See also the discussion in the Jenkins Google Group:
      https://groups.google.com/forum/#!topic/jenkinsci-users/8hXjxAB0WSw

          [JENKINS-25760] Jenkins maven-plugin cannot deal with mavens advanced reactor options

          Jacques Stadler created issue -
          Jacques Stadler made changes -
          Description Original: The Jenkins Maven Plugin cannot deal with the advanced reactor options of Maven.
          See http://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options

          When e.g. executing a a maven build with the following maven command in Jenkins:
          mvn clean install -pl !excludedModule

          one gets the following error:
          {code}
          Executing Maven: -B -f /myworkspace/myproject/pom.xml clean install -pl !excludedModule
          [INFO] Scanning for projects...
          [ERROR] Could not find the selected project in the reactor: !excludedModule -> [Help 1]
          [ERROR]
          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
          [ERROR] Re-run Maven using the -X switch to enable full debug logging.
          [ERROR]
          [ERROR] For more information about the errors and possible solutions, please read the following articles:
          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
          channel stopped
          {code}

          See also the discussion in the Jenkins Google Group:
          https://groups.google.com/forum/#!topic/jenkinsci-users/8hXjxAB0WSw
          New: The Jenkins Maven Plugin cannot deal with the advanced reactor options of Maven.
          See http://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options

          When e.g. executing a a maven build with the following maven command in Jenkins:
          mvn clean install -pl !excludedModule

          one gets the following error:
          {code}
          Executing Maven: -B -f /myworkspace/myproject/pom.xml clean install -pl !excludedModule
          [INFO] Scanning for projects...
          [ERROR] Could not find the selected project in the reactor: !excludedModule -> [Help 1]
          [ERROR]
          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
          [ERROR] Re-run Maven using the -X switch to enable full debug logging.
          [ERROR]
          [ERROR] For more information about the errors and possible solutions, please read the following articles:
          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
          channel stopped
          {code}

          Running the same command on the same project with the same maven version on the command line it works fine.

          See also the discussion in the Jenkins Google Group:
          https://groups.google.com/forum/#!topic/jenkinsci-users/8hXjxAB0WSw
          Maxsoel Alberton made changes -
          Link New: This issue is duplicated by JENKINS-26472 [ JENKINS-26472 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 159738 ] New: JNJira + In-Review [ 180102 ]

            Unassigned Unassigned
            jstadler Jacques Stadler
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: