[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens closed an issue as Not A Defect Turns out the maven plugin used was waay old. Now using version 2.14 and it works fine. Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Change By: Harm Doedens Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens updated an issue Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Change By: Harm Doedens Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens commented on JENKINS-41221 Re: Maven build with pom.xml in subfolder fails 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title
Harm Doedens updated an issue
Jenkins / JENKINS-41221
Maven build with pom.xml in subfolder fails
Change By:
Harm Doedens
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 */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:{code}[workspace] $ /bin/sh -xe /tmp/hudson7796811335066889247.sh+ mvn --versionApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)Maven home: /usr/local/apache-mavenJava version: 1.8.0_112, vendor: Oracle CorporationJava home: /usr/java/jdk1.8.0_112/jreDefault locale: en_US, platform encoding: UTF-8OS name: "linux", version: "4.1.12-61.1.25.el7uek.x86_64", arch: "amd64", family: "unix"Parsing POMsFATAL: nulljava.lang.StackOverflowError at java.lang.Exception.(Exception.java:102) at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.(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 buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsFinished: FAILURE{code}
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens updated an issue Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Change By: Harm Doedens Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens created an issue Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2017/Jan/19 4:00 PM 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 Labels: maven Priority: Major Reporter: Harm Doedens 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 /pom.xml 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
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title
Harm Doedens updated an issue
Jenkins / JENKINS-41221
Maven build with pom.xml in subfolder fails
Change By:
Harm Doedens
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' _Root POM_ option as * /pom.xml * This jenkins build gives me an error with the following output:{code}[workspace] $ /bin/sh -xe /tmp/hudson7796811335066889247.sh+ mvn --versionApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)Maven home: /usr/local/apache-mavenJava version: 1.8.0_112, vendor: Oracle CorporationJava home: /usr/java/jdk1.8.0_112/jreDefault locale: en_US, platform encoding: UTF-8OS name: "linux", version: "4.1.12-61.1.25.el7uek.x86_64", arch: "amd64", family: "unix"Parsing POMsFATAL: nulljava.lang.StackOverflowError at java.lang.Exception.(Exception.java:102) at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.(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 buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsFinished: FAILURE{code}
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title Harm Doedens commented on JENKINS-24686 Re: scm-sync-configuration fails if job name contains whitespace There already is a pull request in which this issue is fixed. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/31 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
