Maven: Non-resolvable parent POM

Maven Module Build Automation Parent Child

Maven Problem Overview

I have my maven project setup as 1 shell projects and 4 children modules. When I try to build the shell. I get:

[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR] The project module1:1.0_A0 (C:\module1\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Failure to find shell:pom:1.0_A0 in http://nyhub1.ny.ssmb.com:8081/nexus/content/repositories/JBoss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 11 -> [Help 2]

If I try to build a lone module I get the same error only replace module1, with whatever module it was.

Have them all referencing the parent in their poms.

<parent>
	<artifactId>shell</artifactId>
	<groupId>converter</groupId>
	<version>1.0_A0</version>
</parent>

Here is the relevant parts of the shell pom:

<groupId>converter</groupId>
<artifactId>shell</artifactId>
<version>1.0_A0</version>
<packaging>pom</packaging>
<name>shell</name>


<modules>
    <module>module1</module>
    <module>module2</module>
    <module>module3</module>
    <module>module4</module>
</modules>

Maven Solutions

Solution 1 - Maven

Just for reference.

The joys of Maven.

Putting the relative path of the modules to ../pom.xml solved it.

The parent element has a relativePath element that you need to point to the directory of the parent. It defaults to ..

Solution 2 - Maven

It can also be fixed by putting the correct settings.xml file into the ~/.m2/ directory.

Solution 3 - Maven

Alternative reason also might be the parent artifact comes from repository which is not accessible from pom.xml, typically private repository. The solution was to provide that repository in pom.xml:

<repositories>
    <repository>
        <id>internal-repo</id>
        <name>internal repository</name>
        <url>https://my/private/repo</url>
        <layout>default</layout>
        <releases>
            <enabled>true</enabled>
        </releases>
        <snapshots>
            <enabled>true</enabled>
        </snapshots>
    </repository>
</repositories>

In my case the problem was even more complicated due to Eclipse: the repository was active only in special profile (<profiles><profile><id>activate-private-repo</id><repositories>...) and Maven GUI in Eclipse didn't allow to set this profile through Ctrl+Alt+P shortcut.

The solution was to temporarily declare repository outside profile (unconditionally), launch Alt+F5 Maven Update Project, activate profile and put repository declaration back into profile. This is rather Eclipse bug, not Maven bug.

Solution 4 - Maven

Just add <relativePath /> so the parent in pom should look like:

<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.0.4.RELEASE</version>
		<relativePath />
	</parent>

Solution 5 - Maven

Non-resolvable parent POM: This means you cannot resolve the parent repo.

Trun on debug mode:

[DEBUG] Reading global settings from **/usr/local/Cellar/maven/3.5.4/libexec/conf/settings.xml**
[DEBUG] **Reading user settings from /Users/username/.m2/settings.xml**
[DEBUG] Reading global toolchains from /usr/local/Cellar/maven/3.5.4/libexec/conf/toolchains.xml
[DEBUG] Reading user toolchains from /Users/username/.m2/toolchains.xml
[DEBUG] Using local repository at /Users/username/.m2/repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /Users/username/.m2/repository
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:

Because the parent repo is not part of the maven central. The solution is specify a setting.xml in ~m2/ to help result the parent POM. /Users/username/.m2/settings.xml

In that XML, you might need to specify the repository information.

Solution 6 - Maven

verify if You have correct values in child POMs

GroupId
ArtefactId
Version

In Eclipse, for example, You can search for it:

Solution 7 - Maven

Replace <version>1.0_A0</version> with <version>${project.version}</version>

Run mvn once. This will download all the required repositories. You may switch back to 1.0_A0 after this step.

Solution 8 - Maven

`<relativePath>`

If you build under a child project, then <relativePath> can help you resolve the parent pom.

install parent pom

But if you build the child project out of its folder, <relativePath> doesn't work. You can install the parent pom into your local repository first, then build the child project.

Solution 9 - Maven

I had similar problem at my work.

Building the parent project without dependency created parent_project.pom file in the .m2 folder.

Then add the child module in the parent POM and run Maven build.

<modules>
    <module>module1</module>
    <module>module2</module>
    <module>module3</module>
    <module>module4</module>
</modules>

Solution 10 - Maven

It was fixed when I removed settings.xml from .m2 folder.

Solution 11 - Maven

I had the following config in the parent pom:

  <properties>
    <revision>1.0-SNAPSHOT</revision>
  </properties>

  <groupId>com.company.org</groupId>
  <artifactId>api-reactor-pom</artifactId>
  <version>$revision</version>
  <packaging>pom</packaging>

And I was getting 'Non-resolvable parent POM' error. I changed version to <version>1.0-SNAPSHOT</version>, and it's gone.

Apache Maven 3.6.3.

Solution 12 - Maven

In this case the parent artifact is not found. As others pointed out, adding <relativePath/> to the pom where you reference a parent that cannot be found locally may work. But why does it work?

> If the parent POM is not located in the parent folder, we need to use > the relativePath tag to refer to the location. >... > To skip the local file search and directly search the parent POM > in Maven repositories, we need to explicitly set the relativePath to > an empty value

as they explained here.

In other cases it will not work because the real reason is that Maven is unable to find the settings.xml which specifies the repositories to check for the parent artifact. E.g. when you try to build your Maven project from WSL2 (Linux shell on Windows) where you have not set up your Maven configuration.

In that case you need to create the settings.xml in the .m2 directory of WSL2 or create a reference to it, e.g. via a symbolic link. (That is a different issue but could be solved like this.)

Solution 13 - Maven

Add a Dependency in

pom.xml:

<parent>
	<groupId>org.springframework.boot</groupId>
	<artifactId>spring-boot-starter-parent</artifactId>
	<version>2.1.8.RELEASE</version>
	<relativePath/> <!-- lookup parent from repository -->
</parent>
<dependency>
	    <groupId>org.apache.maven.plugins</groupId>
	    <artifactId>maven-resources-plugin</artifactId>
	    <version>2.4.3</version>
</dependency>

Solution 14 - Maven

I solved that problem on me after a very long try, I created another file named "parent_pom.xml" in child module file directory at local and pasted contents of parent_pom.xml,which is located at remote, to newly created "parent_pom.xml". It worked for me and error message has gone.

Solution 15 - Maven

Inside relative path tag do as follows

<relative>{project_name}/pom.xml</relative>

and then RunAs-> Maven build

It worked for me.

Solution 16 - Maven

In addition to the answer by Luke Willis, looks like this:

<parent>
    <groupId>com.example</groupId>
    <artifactId>some-module</artifactId>
    <version>1.0</version>
    <relativePath>../pom.xml</relativePath>
</parent>

Solution 17 - Maven

I had the issue that two reactor build pom.xml files had the same artefactId.

Content Type	Original Author	Original Content on Stackoverflow
Question	Will	View Question on Stackoverflow
Solution 1 - Maven	Will	View Answer on Stackoverflow
Solution 2 - Maven	user1747134	View Answer on Stackoverflow
Solution 3 - Maven	Tomáš Záluský	View Answer on Stackoverflow
Solution 4 - Maven	stakowerflol	View Answer on Stackoverflow
Solution 5 - Maven	Wu Yongchao	View Answer on Stackoverflow
Solution 6 - Maven	cane	View Answer on Stackoverflow
Solution 7 - Maven	Prasanth Pennepalli	View Answer on Stackoverflow
Solution 8 - Maven	Hawk	View Answer on Stackoverflow
Solution 9 - Maven	Prabhu	View Answer on Stackoverflow
Solution 10 - Maven	Ninad Pingale	View Answer on Stackoverflow
Solution 11 - Maven	vladk	View Answer on Stackoverflow
Solution 12 - Maven	Balu	View Answer on Stackoverflow
Solution 13 - Maven	Siva	View Answer on Stackoverflow
Solution 14 - Maven	Ozan Apaydın	View Answer on Stackoverflow
Solution 15 - Maven	Sanket Dhumal	View Answer on Stackoverflow
Solution 16 - Maven	Valeriy Emelyanov	View Answer on Stackoverflow
Solution 17 - Maven	benez	View Answer on Stackoverflow