[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized

6 views
Skip to first unread message

benjamin.brummer@pinteam.eu (JIRA)

unread,
Mar 15, 2019, 5:36:03 AM3/15/19
to jenkinsc...@googlegroups.com
Benjamin Brummer created an issue
 
Jenkins / Bug JENKINS-56579
.mvn/extensions.xml not recognized
Issue Type: Bug Bug
Assignee: Olivier Lamy
Components: maven-invoker-plugin
Created: 2019-03-15 09:35
Environment: jenkins 2.164.1
Priority: Minor Minor
Reporter: Benjamin Brummer

We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine.

The pom.xml is in a subfolder next to the .mvn/extensions.xml

This job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to.

 

We could reproduce this issue with the tycho-example form here too https://github.com/vogellacompany/tycho-example

3.3.9 + code in "sub"

[Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9\bin\mvn.cmd clean verify -V -B --file sub/pom.xml && exit %%ERRORLEVEL%%"
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9
Java version: 1.8.0_202, vendor: Oracle Corporation
Java home: c:\jenkins\tools\hudson.model.JDK\8\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.rcp\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.p2.ui\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\features\com.vogella.tycho.feature\pom.xml of C:\jenkins\workspace\Vogella\sub\features\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.plugin1.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ 
[ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.rcp.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ 
 @ 
[ERROR] The build could not read 3 projects -> [Help 1]
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.bundles:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\sub\bundles\pom.xml) has 4 errors
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.rcp\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.p2.ui\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.features:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\sub\features\pom.xml) has 1 error
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\features\com.vogella.tycho.feature\pom.xml of C:\jenkins\workspace\Vogella\sub\features\pom.xml does not exist
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.tests:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\sub\tests\pom.xml) has 2 errors
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.plugin1.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist
[ERROR]     Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.rcp.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist
[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/ProjectBuildingException
Build step 'Invoke top-level Maven targets' marked build as failure
Finished: FAILURE

3.6.0 and code in root

[Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.6.0\bin\mvn.cmd clean verify -V -B && exit %%ERRORLEVEL%%"
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)
Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.6.0\bin\..
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: c:\jenkins\tools\hudson.model.JDK\8\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10
[FATAL] Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10
[FATAL] Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10
[FATAL] Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10
 @ 
[ERROR] The build could not read 4 projects -> [Help 1]
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.bundles:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\bundles\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10 -> [Help 2]
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.features:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\features\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10 -> [Help 2]
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.tests:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\tests\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10 -> [Help 2]
[ERROR]   
[ERROR]   The project com.vogella.tycho:com.vogella.tycho.releng:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\releng\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT: Could not find artifact com.vogella.tycho:com.vogella.tycho.configuration:pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ com.vogella.tycho:com.vogella.tycho.root:1.0.0-SNAPSHOT, C:\jenkins\workspace\Vogella\pom.xml, line 7, column 10 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Build step 'Invoke top-level Maven targets' marked build as failureFinished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

benjamin.brummer@pinteam.eu (JIRA)

unread,
Mar 15, 2019, 5:44:03 AM3/15/19
to jenkinsc...@googlegroups.com
Benjamin Brummer updated an issue
Change By: Benjamin Brummer
Environment: jenkins 2.164.1
maven-invoker-plugin 2.4

ubuntu 18.04.2 master
windows 7 slaves

benjamin.brummer@pinteam.eu (JIRA)

unread,
Mar 15, 2019, 7:11:02 AM3/15/19
to jenkinsc...@googlegroups.com
Benjamin Brummer commented on Bug JENKINS-56579
 
Re: .mvn/extensions.xml not recognized

Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory.

benjamin.brummer@pinteam.eu (JIRA)

unread,
Mar 15, 2019, 7:22:01 AM3/15/19
to jenkinsc...@googlegroups.com
Benjamin Brummer edited a comment on Bug JENKINS-56579
 
Re: .mvn/extensions.xml not recognized
* Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory.
* Windows 10 Agent fails

benjamin.brummer@pinteam.eu (JIRA)

unread,
Mar 15, 2019, 7:42:02 AM3/15/19
to jenkinsc...@googlegroups.com
Benjamin Brummer edited a comment on Bug JENKINS-56579
* Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory.
* Windows 10 Agent fails

* Ubuntu agent is fine

So looks like a Windows problem.

benjamin-buescher@web.de (JIRA)

unread,
Apr 9, 2019, 8:23:02 AM4/9/19
to jenkinsc...@googlegroups.com
Benjamin Büscher commented on Bug JENKINS-56579
 
Re: .mvn/extensions.xml not recognized

I think I ran into the same issue but from a slightly different direction. I also have a pomless tycho build running on Windows slaves.

  • I call maven via CMD, not the jenkins maven plugin. (-> I dont think its a jenkins issue)
    • This build fails on maven 3.6.0 with similar looking log and works on maven 3.3.9, just as described here.
  • I've set up a local jenkins on my dev machine (win10) - this build works fine using maven 3.6.0!

My guess is that this is a maven issue on win server, probably related to how plugins like tycho are loaded. 

benjamin.brummer@pinteam.eu (JIRA)

unread,
Apr 9, 2019, 8:33:02 AM4/9/19
to jenkinsc...@googlegroups.com
Benjamin Brummer commented on Bug JENKINS-56579
 
Re: .mvn/extensions.xml not recognized

"I call maven via CMD, not the jenkins maven plugin" => Without jenkins involved at all? Without jenkins it works here with 3.6.0.

Useing a Jenkins agent => No matter how we call mvn, it fails.

benjamin.brummer@pinteam.eu (JIRA)

unread,
Apr 9, 2019, 8:49:02 AM4/9/19
to jenkinsc...@googlegroups.com
Benjamin Brummer updated an issue
We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine.

The pom.xml is in a subfolder next to the .mvn/extensions.xml

This job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to too .

 

We could reproduce this issue with the tycho-example form here too [https://github.com/vogellacompany/tycho-example]
h1. 3.3.9 + code in "sub"
{code:java}
{code}
h1. 3.6.0 and code in root
{code:java}
{code}

benjamin-buescher@web.de (JIRA)

unread,
Apr 9, 2019, 8:57:01 AM4/9/19
to jenkinsc...@googlegroups.com
Benjamin Büscher commented on Bug JENKINS-56579
 
Re: .mvn/extensions.xml not recognized

It's a little ugly: jenkins -> ant -> cmd -> maven:

Jenkins calls an ant build via ant plugin. Inside of the ant build an exec target is used to call cmd launching the maven build.

benjamin.brummer@pinteam.eu (JIRA)

unread,
May 28, 2019, 11:51:03 AM5/28/19
to jenkinsc...@googlegroups.com
Benjamin Brummer updated Bug JENKINS-56579
 

I can not reproduce the problem anymore. All maven versions work now as expected.
Change By: Benjamin Brummer
Status: Open Fixed but Unreleased
Resolution: Cannot Reproduce

benjamin.brummer@pinteam.eu (JIRA)

unread,
May 28, 2019, 11:52:03 AM5/28/19
to jenkinsc...@googlegroups.com
Change By: Benjamin Brummer
Status: Fixed but Unreleased Closed
Reply all
Reply to author
Forward
0 new messages