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 - gt   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 - gt   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    lt parent gt       lt artifactId gt shell lt  artifactId gt       lt groupId gt converter lt  groupId gt       lt version gt 1 0 A0 lt  version gt   lt  parent gt    Here is the relevant parts of the shell pom    lt groupId gt converter lt  groupId gt   lt artifactId gt shell lt  artifactId gt   lt version gt 1 0 A0 lt  version gt   lt packaging gt pom lt  packaging gt   lt name gt shell lt  name gt     lt modules gt       lt module gt module1 lt  module gt       lt module gt module2 lt  module gt       lt module gt module3 lt  module gt       lt module gt module4 lt  module gt   lt  modules gt

User · Answer

Just add  lt relativePath   gt  so the parent in pom should look like    lt parent gt           lt groupId gt org springframework boot lt  groupId gt           lt artifactId gt spring-boot-starter-parent lt  artifactId gt           lt version gt 2 0 4 RELEASE lt  version gt           lt relativePath   gt       lt  parent gt

User · Answer

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

User · Answer

verify if You have correct values in child POMs    GroupId ArtefactId Version   In Eclipse  for example  You can search for it

User · Answer

Inside relative path tag do as follows   lt relative gt  project name  pom xml lt  relative gt    and then RunAs-  Maven build  It worked for me

User · Answer

It was fixed when I removed settings xml from  m2 folder

User · Answer

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

User · Answer

lt relativePath gt   If you build under a child project  then  lt relativePath gt  can help you resolve the parent pom   install parent pom  But if you build the child project out of its folder    lt relativePath gt  doesn t work  You can install the parent pom into your local repository first  then build the child project

User · Answer

Replace 1 0 A0 with    project version   Run mvn once   This will download all the required repositories   You may switch back to 1 0 A0 after this step

User · Answer

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

User · Answer

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

User · Answer

Add a Dependency in   pom xml    lt parent gt       lt groupId gt org springframework boot lt  groupId gt       lt artifactId gt spring-boot-starter-parent lt  artifactId gt       lt version gt 2 1 8 RELEASE lt  version gt       lt relativePath  gt   lt  -- lookup parent from repository -- gt   lt  parent gt   lt dependency gt           lt groupId gt org apache maven plugins lt  groupId gt           lt artifactId gt maven-resources-plugin lt  artifactId gt           lt version gt 2 4 3 lt  version gt   lt  dependency gt

User · Answer

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

User · Answer

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    lt repositories gt       lt repository gt           lt id gt internal-repo lt  id gt           lt name gt internal repository lt  name gt           lt url gt https   my private repo lt  url gt           lt layout gt default lt  layout gt           lt releases gt               lt enabled gt true lt  enabled gt           lt  releases gt           lt snapshots gt               lt enabled gt true lt  enabled gt           lt  snapshots gt       lt  repository gt   lt  repositories gt    In my case the problem was even more complicated due to Eclipse  the repository was active only in special profile   lt profiles gt  lt profile gt  lt id gt activate-private-repo lt  id gt  lt repositories gt      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

User · Answer

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     lt modules gt       lt module gt module1 lt  module gt       lt module gt module2 lt  module gt       lt module gt module3 lt  module gt       lt module gt module4 lt  module gt   lt  modules gt

[maven] Maven: Non-resolvable parent POM

Examples related to maven

Examples related to module

Examples related to build-automation

Examples related to parent-child