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

Maven build with pom.xml in subfolder fails

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: maven-plugin
    • Labels:
    • Environment:
      Jenkins 2.32.1

      Relevant Plugins:
      - maven-plugin: version: 1.521

      OS: Oracle Linux 7.3, 4.1.12-61.1.25.el7uek.x86_64

      Maven version: 3.3.9
    • Similar Issues:

      Description

      I have created two jobs of the maven jobtype. One has a quite common folder structure wheren the pom.xml is in the root of the project. The other one has many folders and each folder contains a pom. Mind you: it is not a modular maven project, every folder contains a stand-alone-ish project.

      When I build the job where the pom.xml is in the root of the workspace it works well.

      When I build the job where the pom is in a subdirectory I configure the Root POM option as <subdir>/pom.xml

      edit: The jobs folder is a symbolic link to another volume (/var/lib/jenkins/jobs to /opt/jenkins_jobs)

      This jenkins build gives me an error with the following output:

      [workspace] $ /bin/sh -xe /tmp/hudson7796811335066889247.sh
      + mvn --version
      Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
      Maven home: /usr/local/apache-maven
      Java version: 1.8.0_112, vendor: Oracle Corporation
      Java home: /usr/java/jdk1.8.0_112/jre
      Default locale: en_US, platform encoding: UTF-8
      OS name: "linux", version: "4.1.12-61.1.25.el7uek.x86_64", arch: "amd64", family: "unix"
      Parsing POMs
      FATAL: null
      java.lang.StackOverflowError
      	at java.lang.Exception.<init>(Exception.java:102)
      	at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89)
      	at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
      	at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
      	at com.sun.proxy.$Proxy108.lookup(Unknown Source)
      	at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
      	at com.sun.proxy.$Proxy108.lookup(Unknown Source)
      	at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      ...
      and so on
      	at com.sun.proxy.$Proxy108.lookup(Unknown Source)
      	at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source)
      Started calculate disk usage of build
      Finished Calculation of disk usage of build in 0 seconds
      Started calculate disk usage of workspace
      Finished Calculation of disk usage of workspace in 0 seconds
      Finished: FAILURE
      

        Attachments

          Activity

          Hide
          hdoedens Harm Doedens added a comment -

          I have removed the symbolic link and replaced with a normal folder, now the build of a maven project from a subfolder works fine. However, this is still an issue as disk space on /var is limited but on /opt it is virtually unlimited.

          Show
          hdoedens Harm Doedens added a comment - I have removed the symbolic link and replaced with a normal folder, now the build of a maven project from a subfolder works fine. However, this is still an issue as disk space on /var is limited but on /opt it is virtually unlimited.
          Hide
          hdoedens Harm Doedens added a comment -

          Turns out the maven plugin used was waay old. Now using version 2.14 and it works fine.

          Show
          hdoedens Harm Doedens added a comment - Turns out the maven plugin used was waay old. Now using version 2.14 and it works fine.

            People

            • Assignee:
              Unassigned
              Reporter:
              hdoedens Harm Doedens
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: