Skip to content

Fix Jenkins POM Freezer "Wrong Relative POM" Error

October 31st, 2017 - ITTutorial

If you get a build error in Jenkins like:

[ERROR] The build could not read 5 projects -> [Help 1]
[ERROR]
[ERROR]   The project com.laurivan.project:project-common:1.0-34-9
              (/var/lib/jenkins/jobs/project/workspace/project-common/frozen.pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not find artifact
                com.laurivan.project:project-container:pom:1.0-6034-79 in nexus-local
                (https://nexus.local/nexus/content/repositories/releases) and 'parent.relativePath'
                points at wrong local POM @ line 3, column 11 -> [Help 2]

Then you have a POM freezing issue with the parent POM. I.e., the Jenkins plugin has failed to freeze the POM version from a 1.0-SNAPSHOT to an actual 1.0-6034-79. A cause can be the plugin expects a certain sequence of tags in the POM and doesn’t find it. In my case, the initial configuration was:

<groupId>com.laurivan.project</groupId>
<artifactId>project-container</artifactId>
<name>gateway-modules</name>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>

and the expected configuration would be something like

<name>gateway-modules</name>
<groupId>com.laurivan.project</groupId>
<artifactId>project-container</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>

Note the sequence group - artifactId - version.

HTH,

Share on
Reddit
Linked in
Whatsapp

A little experiment: