Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7740167
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T08:42:27+00:00 2026-06-01T08:42:27+00:00

I have a Maven multi-module project and I need two different parent POMs in

  • 0

I have a Maven multi-module project and I need two different parent POMs in this build. The first one is the real parent POM for most modules in the project but one module is a demo project which uses the parent POM of a completely different project (because it’s a demo how to use my project to generate code for the second project).

The build works but I get a warning:

[WARNING] 
[WARNING] Some problems were encountered while building the effective model for my_project:my_project.demo:jar:5.0.0-SNAPSHOT
[WARNING] 'parent.relativePath' points at my_project:parent instead of other_project:parent, please verify your project structure @ line 5, column 10
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 

Since other_project is not really a module of my build, it can be anywhere. This means I can’t give a relative path.

How can I fix this warning?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T08:42:29+00:00Added an answer on June 1, 2026 at 8:42 am

    The solution in this case is to set the relativePath to nothing to overwrite the default ../pom.xml:

    <relativePath/>
    
    • Discussion
    • MNG-4687 – Maven should not warn about incorrect parent path when no relativePath is specified)
    • MNG-2026 – Document how parent-child POM relationships, , and works
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Basically, I have a multi-module project consisting of 5 different modules. One of the
I have a multi module project with a parent project A, and two childs
This is my parent pom.xml (part of it) in a multi-module project: ... <build>
I have a Java multi-module Maven project that I want to build an MVN
I have Maven multi-module project with such structure: parent-pom-project -- module1 -- module2 At
I have a multi-module Maven project A. There are two modules: B and C,
I have a multi-module project in maven, where other projects need to use the
I have a maven multi-module project having hierarchy: parent + ota-module + ota-common +
I have a multi-module Maven project with a parent project P and three sub-modules
I have a multi module Maven project, one of its modules has the main

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.