Maven: Non-resolvable parent POM

Question

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>

if anyone is interested, adding `..` under `` worked for me. — kaptan, Jan 23 '19 at 01:31
Relative path is for non-conforming projects not a "solution" when the expectation is a pom in the parent folder of the module should be accessible. — Rick O'Shea, Nov 06 '19 at 23:04
I tried to install ```mvn install``` but terminals says The term 'mvn' is not recognized as the name of a cmdlet, function, script file, or operable program. — Manghud, Dec 02 '20 at 08:39

score 127 · Accepted Answer · edited Oct 04 '17 at 22:20

127

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 ..

edited Oct 04 '17 at 22:20

Luke Willis

8,429
4
46
79

answered Sep 30 '11 at 15:40

Will

8,246
16
60
92

21

Yes. Using Maven requires that you know what you do, trial and error won't get you very far. On the other hand there are several good references available. This is [one](http://www.sonatype.com/books/mvnref-book/reference/). – Nicola Musatti Sep 30 '11 at 15:46
9

So you added this `..` under `` ? – bsky Jan 04 '17 at 18:43
1

Thanks I tried it for a while to solve the problem. I took the relative path from `../pom.xml` to `..//pom.xml`. – Mario Kurzweil Feb 04 '17 at 19:36
1

Putting the would not necessary solve the problem if you are pointing to a private repository. Look down for Tomáš Záluský response for detail explanation. – Gi1ber7 Aug 15 '18 at 18:50
I'm trying to extend my main pom file to another one (for tests) in the same directory (same project). But this doesn't solve this error. Any idea how to fix it? – Praneeth Peiris Apr 05 '19 at 09:26

score 55 · Answer 2 · edited Sep 01 '17 at 13:09

55

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

edited Sep 01 '17 at 13:09

eggonlegs

1,824
2
23
34

answered May 02 '16 at 12:06

user1747134

2,374
1
19
26

4

Exactly that solved my problem, thanks!!! But not by putting it into some directory, but pointing Eclipse to it in Preferences - Maven - User Settings. – Brain Oct 04 '17 at 13:44
Solved my problem too. Just have to make sure the settings are properly configured to `maven.repo` too.. – Saran May 09 '18 at 00:35
I removed the stting.xml file and fixed. – menoktaokan Apr 14 '21 at 11:28

score 27 · Answer 3 · answered Apr 18 '16 at 16:08

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.

Same situation!private repo not added to the pom. – LoranceChen Jan 25 '18 at 07:21 — LoranceChen, Jan 25 '18 at 07:21

score 9 · Answer 4 · answered Aug 13 '18 at 07:55

9

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>

answered Aug 13 '18 at 07:55

stakowerflol

979
1
11
20

5

This only applies when the parent is not in the same dir structure, i.e. in a remote repository. – Ondra Žižka Aug 11 '19 at 08:17

Wu Yongchao · Answer 5 · 2018-10-13T10:35:59.283

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.

Awesome ! Adding my repo details in settings xml worked. But why it's not taking from the pom xml (which has the same repo added in it) ? — smilyface, Dec 18 '18 at 13:25

score 4 · Answer 6 · answered Feb 15 '19 at 04:50

`<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.

score 3 · Answer 7 · answered Dec 16 '21 at 12:23

3

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>

answered Dec 16 '21 at 12:23

Valeriy Emelyanov

221
2
6

score 2 · Answer 8 · answered May 07 '16 at 17:53

2

verify if You have correct values in child POMs

GroupId
ArtefactId
Version

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

answered May 07 '16 at 17:53

cane

892
1
10
16

score 2 · Answer 9 · edited May 04 '22 at 13:41

2

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.

edited May 04 '22 at 13:41

FortyTwo

2,414
3
22
33

answered Aug 09 '17 at 00:17

Prasanth Pennepalli

1,018
10
11

1

This only works if the required parent POM has the same version as the sub-module's POM. This is not always the case. – Gerold Broser Feb 09 '18 at 20:14

score 2 · Answer 10 · answered Oct 21 '20 at 15:42

2

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

answered Oct 21 '20 at 15:42

Ninad Pingale

6,801
5
32
55

2

How did you fix? What did you do, do you remember? – menoktaokan Apr 15 '21 at 14:06

score 2 · Answer 11 · answered May 13 '21 at 01:15

2

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.

answered May 13 '21 at 01:15

vladk

29
2

This was my issue. Looks like a bug to me, but you can't use `${revision}` as the version of the parent (even in Maven 3.8.4), and have it resolved locally. – Tony the Tech Mar 06 '23 at 23:46

score 2 · Answer 12 · answered Nov 08 '21 at 14:21

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.)

score 1 · Answer 13 · answered Feb 28 '18 at 15:27

1

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>

answered Feb 28 '18 at 15:27

Prabhu

36
3

Your answer, together with ** solved the problem for me. *relativePath alone did not. – Gyro Gearloose Sep 02 '20 at 10:35

score 0 · Answer 14 · answered Apr 28 '20 at 22:36

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.

score 0 · Answer 15 · answered May 11 '20 at 14:11

0

Inside relative path tag do as follows

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

and then RunAs-> Maven build

It worked for me.

answered May 11 '20 at 14:11

Sanket Dhumal

1
1

2

Where did you locate the relative? relative between relativePath is not allowed – menoktaokan Apr 15 '21 at 14:08

score 0 · Answer 16 · answered Mar 09 '23 at 08:29

0

I had this issue, the version of the parent pom.xml was not the same as the child's ones after an upgrade.

I Fixed it by setting the same version number for the parent and it's childs.

answered Mar 09 '23 at 08:29

Ben

308
1
4
11

score -2 · Answer 17 · answered Mar 23 '18 at 16:04

-2

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

answered Mar 23 '18 at 16:04

benez

1,856
22
28

In my case, this parent module was not in the parent folder, I had to add in the child module ../parent-module-dir – Rolintocour Oct 30 '18 at 14:01

Shiva Perumalsamy · Answer 18 · 2019-09-19T06:12:17.073

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>

Maven: Non-resolvable parent POM

18 Answers18

`<relativePath>`

install parent pom

Linked