You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andre Gomes <an...@hotmail.com> on 2012/11/01 23:10:04 UTC
Maven site can not find parent
I am using the maven-site-plugin version 3.2 in a multi-module project that has a parent project. This parent project is a release and it is in a release repository and it is in this project that is defined the repositories (that is also defined in the settings.xml file). The multi-module project is a snapshot and when I run mvn site on the multi-module project I am getting the error below saying that can not find the parent project, however the parent project is download. When I change the parent project version to a snapshot version the error disappear, also when I run mvn install in the parent project the error disappear. What I want to know is why I am getting this error and how can I solved without changing the parent version and running mvn install in the parent.
Note: In the pom files the relative path is set as empty. And all project have the same groupId
Thanks, André Gomes
[INFO] Parent project loaded from repository:groupId:parent:pom:1.0.3[DEBUG] Parent project loaded ...[DEBUG] Skipped site descriptor for locale en[DEBUG] Skipped remote site descriptor check[WARNING] Unable to find a URL to the parent project. The parent menuwill NOT be added.[DEBUG] Attempting to load module information from local filesystem[DEBUG] Verifying availabilityof /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom from [central (http://repo1.maven.org/maven2, releases)][DEBUG] Skipped remote update check forgroupId:parent:pom:1.0.3, locally cached artifactup-to-date.[DEBUG] Using connector WagonRepositoryConnector with priority 0 forhttp://repo1.maven.org/maven2Downloading:http://repo1.maven.org/maven2/groupId/parent/1.0.3/parent-1.0.3.pom[DEBUG] Reading resolution trackingfile /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom.lastUpdated[DEBUG] Writing resolution trackingfile /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom.lastUpdated[INFO]------------------------------------------------------------------------[INFO] Reactor Summary:[INFO] [INFO] projectName .............................................. FAILURE[12.552s][INFO] moduleA ........................................ SKIPPED[INFO] moduleB ....................................... SKIPPED[INFO] moduleC ................................ SKIPPED[INFO] moduleD ........................... SKIPPED[INFO] moduleE .......................................... SKIPPED[INFO] moduleF ................................... SKIPPED[INFO]------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO]------------------------------------------------------------------------[INFO] Total time: 13.045s[INFO] Finished at: Tue Oct 30 18:39:43 WET 2012[INFO] Final Memory: 26M/247M[INFO]------------------------------------------------------------------------[ERROR] Failed to execute goalorg.apache.maven.plugins:maven-site-plugin:3.1:site (default-site) onproject projectName: SiteToolException: Unable to read local module-POM: 1problem was encountered while building the effective model forgroupId:moduleA:1.1.5-SNAPSHOT[ERROR] [FATAL] Non-resolvable parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2) @groupId:projectName:1.1.5-SNAPSHOT, /home/agomes/workspace/projectName/pom.xml,line 9, column 10[ERROR] for project groupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml for projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml[ERROR] -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed toexecute goal org.apache.maven.plugins:maven-site-plugin:3.1:site(default-site) on project projectName: SiteToolException: Unable to read localmodule-POMatorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)atorg.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)atorg.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:616)atorg.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)atorg.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)atorg.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused by: org.apache.maven.plugin.MojoExecutionException:SiteToolException: Unable to read local module-POMatorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:300)atorg.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)atorg.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)... 19 moreCaused by: org.apache.maven.doxia.tools.SiteToolException: Unable toread local module-POMatorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:892)atorg.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)atorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:293)... 23 moreCaused by: org.apache.maven.project.InvalidProjectModelException: 1problem was encountered while building the effective model forgroupId:moduleA:1.1.5-SNAPSHOT[FATAL] Non-resolvable parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2) @groupId:projectName:1.1.5-SNAPSHOT, /home/agomes/workspace/projectName/pom.xml,line 9, column 10for project groupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml for projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xmlatorg.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:194)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:211)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:223)atorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:888)... 25 more
Re: Maven site can not find parent
Posted by Curtis Rueden <ct...@wisc.edu>.
Hi Chad et. al,
> It seems that lots of things in the maven world make the assumption
> that the aggregator pom and the parent pom are one and the same.
Indeed, there are some issues with it. For example:
http://jira.codehaus.org/browse/MNG-4687
Regards,
Curtis
On Tue, Nov 13, 2012 at 12:11 PM, Davis, Chad <Ch...@emc.com> wrote:
>
> > > Concerning the empty "relativePath" element, this will typically be
> > > empty when you can't guarantee that the parent is in the parent
> > > directory. it's a common practice to separate the responsibilities of
> > > the aggregator pom from the parent pom. When that is the case, if you
> > > don't have the empty "relativePath" element, it will fail.
> > >
> >
> > To make this a bit clearer: if you use a *released* parent pom, it won't
> have a
> > relative path. If this is true in a module, you need an empty element.
> And the
> > site plugin may become disoriented.
> >
>
> It seems that lots of things in the maven world make the assumption that
> the aggregator pom and the parent pom are one and the same. I've been
> having trouble with this parent pom resolution issue in the Hudson/Jenkins
> environment for some time. In these cases, it's the build server's own pom
> processing that can't seem to be able to resolve where the parent pom is.
> I think this has improved on newer versions of the build servers though.
>
RE: Maven site can not find parent
Posted by "Davis, Chad" <Ch...@emc.com>.
> > Concerning the empty "relativePath" element, this will typically be
> > empty when you can't guarantee that the parent is in the parent
> > directory. it's a common practice to separate the responsibilities of
> > the aggregator pom from the parent pom. When that is the case, if you
> > don't have the empty "relativePath" element, it will fail.
> >
>
> To make this a bit clearer: if you use a *released* parent pom, it won't have a
> relative path. If this is true in a module, you need an empty element. And the
> site plugin may become disoriented.
>
It seems that lots of things in the maven world make the assumption that the aggregator pom and the parent pom are one and the same. I've been having trouble with this parent pom resolution issue in the Hudson/Jenkins environment for some time. In these cases, it's the build server's own pom processing that can't seem to be able to resolve where the parent pom is. I think this has improved on newer versions of the build servers though.
Re: Maven site can not find parent
Posted by Benson Margulies <bi...@gmail.com>.
On Mon, Nov 12, 2012 at 1:42 PM, David Karr <da...@gmail.com>wrote:
> Concerning the empty "relativePath" element, this will typically be empty
> when you can't guarantee that the parent is in the parent directory. it's
> a common practice to separate the responsibilities of the aggregator pom
> from the parent pom. When that is the case, if you don't have the empty
> "relativePath" element, it will fail.
>
To make this a bit clearer: if you use a *released* parent pom, it won't
have a relative path. If this is true in a module, you need an empty
element. And the site plugin may become disoriented.
>
>
> On Sat, Nov 10, 2012 at 3:06 PM, Dennis Lundberg <de...@apache.org>
> wrote:
>
> > Hi
> >
> > Why do you use an empty <relativePath> element?
> >
> > If the parent is in the directory above the current project, then just
> > omit the <relativePath> element. Otherwise it must contain the relative
> > path to the directory where the parent pom is.
> >
> > On 2012-11-01 23:10, Andre Gomes wrote:
> > >
> > > I am using the maven-site-plugin version 3.2 in a multi-module project
> > that has a parent project. This parent project is a release and it is in
> a
> > release repository and it is in this project that is defined the
> > repositories (that is also defined in the settings.xml file). The
> > multi-module project is a snapshot and when I run mvn site on the
> > multi-module project I am getting the error below saying that can not
> find
> > the parent project, however the parent project is download. When I change
> > the parent project version to a snapshot version the error disappear,
> also
> > when I run mvn install in the parent project the error disappear. What I
> > want to know is why I am getting this error and how can I solved without
> > changing the parent version and running mvn install in the parent.
> > > Note: In the pom files the relative path is set as empty. And all
> > project have the same groupId
> > >
> > > Thanks, André Gomes
> > >
> > > [INFO] Parent project loaded from
> > repository:groupId:parent:pom:1.0.3[DEBUG] Parent project loaded
> ...[DEBUG]
> > Skipped site descriptor for locale en[DEBUG] Skipped remote site
> descriptor
> > check[WARNING] Unable to find a URL to the parent project. The parent
> > menuwill NOT be added.[DEBUG] Attempting to load module information from
> > local filesystem[DEBUG] Verifying availabilityof
> > /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom from
> > [central (http://repo1.maven.org/maven2, releases)][DEBUG] Skipped
> remote
> > update check forgroupId:parent:pom:1.0.3, locally cached
> > artifactup-to-date.[DEBUG] Using connector WagonRepositoryConnector with
> > priority 0 forhttp://
> >
> repo1.maven.org/maven2Downloading:http://repo1.maven.org/maven2/groupId/parent/1.0.3/parent-1.0.3.pom[DEBUG]Readingresolution trackingfile
> >
> /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom.lastUpdated[DEBUG]
> > Writing resolution trackingfile
> > /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-
> > 1.0.3.p
> >
> om.lastUpdated[INFO]------------------------------------------------------------------------[INFO]
> > Reactor Summary:[INFO] [INFO] projectName
> > .............................................. FAILURE[12.552s][INFO]
> > moduleA ........................................ SKIPPED[INFO] moduleB
> > ....................................... SKIPPED[INFO] moduleC
> > ................................ SKIPPED[INFO] moduleD
> > ........................... SKIPPED[INFO] moduleE
> > .......................................... SKIPPED[INFO] moduleF
> > ...................................
> >
> SKIPPED[INFO]------------------------------------------------------------------------[INFO]
> > BUILD
> >
> FAILURE[INFO]------------------------------------------------------------------------[INFO]
> > Total time: 13.045s[INFO] Finished at: Tue Oct 30 18:39:43 WET 2012[INFO]
> > Final Memory:
> >
> 26M/247M[INFO]------------------------------------------------------------------------[ERROR]
> > Failed to execute goalorg.apache.maven.plugins:maven-site-plugin:3.
> > 1:site (
> > default-site) onproject projectName: SiteToolException: Unable to read
> > local module-POM: 1problem was encountered while building the effective
> > model forgroupId:moduleA:1.1.5-SNAPSHOT[ERROR] [FATAL] Non-resolvable
> > parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find
> > artifactgroupId:parent:pom:1.0.3 in central(
> http://repo1.maven.org/maven2)
> > @groupId:projectName:1.1.5-SNAPSHOT,
> > /home/agomes/workspace/projectName/pom.xml,line 9, column 10[ERROR] for
> > project groupId:moduleA:1.1.5-SNAPSHOTat
> > /home/agomes/workspace/projectName/moduleA/pom.xml for
> > projectgroupId:moduleA:1.1.5-SNAPSHOTat
> > /home/agomes/workspace/projectName/moduleA/pom.xml[ERROR] -> [Help
> > 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> toexecute
> > goal org.apache.maven.plugins:maven-site-plugin:3.1:site(default-site) on
> > project projectName: SiteToolException: Unable to read
> >
> localmodule-POMatorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)atorg.apache.maven.lifecy
> > cle.inte
> >
> rnal.MojoExecutor.execute(MojoExecutor.java:153)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)atorg.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)atorg.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)at
> > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)at
> > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)at
> > org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at
> > org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at
> > org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >
> Method)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.Deleg
> > atingMet
> > hodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at
> >
> java.lang.reflect.Method.invoke(Method.java:616)atorg.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)atorg.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)atorg.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused
> > by: org.apache.maven.plugin.MojoExecutionException:SiteToolException:
> > Unable to read local
> >
> module-POMatorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:300)atorg.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)at
> >
> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)atorg.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)...
> > 19
> > moreCaus
> > ed by: org.apache.maven.doxia.tools.SiteToolException: Unable toread
> local
> >
> module-POMatorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:892)atorg.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)atorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:293)...
> > 23 moreCaused by: org.apache.maven.project.InvalidProjectModelException:
> > 1problem was encountered while building the effective model
> > forgroupId:moduleA:1.1.5-SNAPSHOT[FATAL] Non-resolvable parent POM
> > forgroupId:projectName:1.1.5-SNAPSHOT: Could not find
> > artifactgroupId:parent:pom:1.0.3 in central(
> http://repo1.maven.org/maven2)
> > @groupId:projectName:1.1.5-SNAPSHOT,
> > /home/agomes/workspace/projectName/pom.xml,line 9, column 10for project
> > groupId:moduleA:1.1.5-SNAPSHOTat
> > /home/agomes/workspace/projectName/moduleA/pom.xml for
> > projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectNa
> > me/modul
> >
> eA/pom.xmlatorg.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:194)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:211)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:223)atorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:888)...
> > 25 more
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
Re: Maven site can not find parent
Posted by David Karr <da...@gmail.com>.
Concerning the empty "relativePath" element, this will typically be empty
when you can't guarantee that the parent is in the parent directory. it's
a common practice to separate the responsibilities of the aggregator pom
from the parent pom. When that is the case, if you don't have the empty
"relativePath" element, it will fail.
On Sat, Nov 10, 2012 at 3:06 PM, Dennis Lundberg <de...@apache.org> wrote:
> Hi
>
> Why do you use an empty <relativePath> element?
>
> If the parent is in the directory above the current project, then just
> omit the <relativePath> element. Otherwise it must contain the relative
> path to the directory where the parent pom is.
>
> On 2012-11-01 23:10, Andre Gomes wrote:
> >
> > I am using the maven-site-plugin version 3.2 in a multi-module project
> that has a parent project. This parent project is a release and it is in a
> release repository and it is in this project that is defined the
> repositories (that is also defined in the settings.xml file). The
> multi-module project is a snapshot and when I run mvn site on the
> multi-module project I am getting the error below saying that can not find
> the parent project, however the parent project is download. When I change
> the parent project version to a snapshot version the error disappear, also
> when I run mvn install in the parent project the error disappear. What I
> want to know is why I am getting this error and how can I solved without
> changing the parent version and running mvn install in the parent.
> > Note: In the pom files the relative path is set as empty. And all
> project have the same groupId
> >
> > Thanks, André Gomes
> >
> > [INFO] Parent project loaded from
> repository:groupId:parent:pom:1.0.3[DEBUG] Parent project loaded ...[DEBUG]
> Skipped site descriptor for locale en[DEBUG] Skipped remote site descriptor
> check[WARNING] Unable to find a URL to the parent project. The parent
> menuwill NOT be added.[DEBUG] Attempting to load module information from
> local filesystem[DEBUG] Verifying availabilityof
> /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom from
> [central (http://repo1.maven.org/maven2, releases)][DEBUG] Skipped remote
> update check forgroupId:parent:pom:1.0.3, locally cached
> artifactup-to-date.[DEBUG] Using connector WagonRepositoryConnector with
> priority 0 forhttp://
> repo1.maven.org/maven2Downloading:http://repo1.maven.org/maven2/groupId/parent/1.0.3/parent-1.0.3.pom[DEBUG]Reading resolution trackingfile
> /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom.lastUpdated[DEBUG]
> Writing resolution trackingfile
> /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-
> 1.0.3.p
> om.lastUpdated[INFO]------------------------------------------------------------------------[INFO]
> Reactor Summary:[INFO] [INFO] projectName
> .............................................. FAILURE[12.552s][INFO]
> moduleA ........................................ SKIPPED[INFO] moduleB
> ....................................... SKIPPED[INFO] moduleC
> ................................ SKIPPED[INFO] moduleD
> ........................... SKIPPED[INFO] moduleE
> .......................................... SKIPPED[INFO] moduleF
> ...................................
> SKIPPED[INFO]------------------------------------------------------------------------[INFO]
> BUILD
> FAILURE[INFO]------------------------------------------------------------------------[INFO]
> Total time: 13.045s[INFO] Finished at: Tue Oct 30 18:39:43 WET 2012[INFO]
> Final Memory:
> 26M/247M[INFO]------------------------------------------------------------------------[ERROR]
> Failed to execute goalorg.apache.maven.plugins:maven-site-plugin:3.
> 1:site (
> default-site) onproject projectName: SiteToolException: Unable to read
> local module-POM: 1problem was encountered while building the effective
> model forgroupId:moduleA:1.1.5-SNAPSHOT[ERROR] [FATAL] Non-resolvable
> parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find
> artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2)
> @groupId:projectName:1.1.5-SNAPSHOT,
> /home/agomes/workspace/projectName/pom.xml,line 9, column 10[ERROR] for
> project groupId:moduleA:1.1.5-SNAPSHOTat
> /home/agomes/workspace/projectName/moduleA/pom.xml for
> projectgroupId:moduleA:1.1.5-SNAPSHOTat
> /home/agomes/workspace/projectName/moduleA/pom.xml[ERROR] -> [Help
> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed toexecute
> goal org.apache.maven.plugins:maven-site-plugin:3.1:site(default-site) on
> project projectName: SiteToolException: Unable to read
> localmodule-POMatorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)atorg.apache.maven.lifecy
> cle.inte
> rnal.MojoExecutor.execute(MojoExecutor.java:153)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)atorg.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)atorg.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.Deleg
> atingMet
> hodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at
> java.lang.reflect.Method.invoke(Method.java:616)atorg.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)atorg.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)atorg.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused
> by: org.apache.maven.plugin.MojoExecutionException:SiteToolException:
> Unable to read local
> module-POMatorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:300)atorg.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)at
> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)atorg.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)...
> 19
> moreCaus
> ed by: org.apache.maven.doxia.tools.SiteToolException: Unable toread local
> module-POMatorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:892)atorg.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)atorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:293)...
> 23 moreCaused by: org.apache.maven.project.InvalidProjectModelException:
> 1problem was encountered while building the effective model
> forgroupId:moduleA:1.1.5-SNAPSHOT[FATAL] Non-resolvable parent POM
> forgroupId:projectName:1.1.5-SNAPSHOT: Could not find
> artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2)
> @groupId:projectName:1.1.5-SNAPSHOT,
> /home/agomes/workspace/projectName/pom.xml,line 9, column 10for project
> groupId:moduleA:1.1.5-SNAPSHOTat
> /home/agomes/workspace/projectName/moduleA/pom.xml for
> projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectNa
> me/modul
> eA/pom.xmlatorg.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:194)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:211)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:223)atorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:888)...
> 25 more
> >
> >
> >
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven site can not find parent
Posted by Dennis Lundberg <de...@apache.org>.
Hi
Why do you use an empty <relativePath> element?
If the parent is in the directory above the current project, then just
omit the <relativePath> element. Otherwise it must contain the relative
path to the directory where the parent pom is.
On 2012-11-01 23:10, Andre Gomes wrote:
>
> I am using the maven-site-plugin version 3.2 in a multi-module project that has a parent project. This parent project is a release and it is in a release repository and it is in this project that is defined the repositories (that is also defined in the settings.xml file). The multi-module project is a snapshot and when I run mvn site on the multi-module project I am getting the error below saying that can not find the parent project, however the parent project is download. When I change the parent project version to a snapshot version the error disappear, also when I run mvn install in the parent project the error disappear. What I want to know is why I am getting this error and how can I solved without changing the parent version and running mvn install in the parent.
> Note: In the pom files the relative path is set as empty. And all project have the same groupId
>
> Thanks, André Gomes
>
> [INFO] Parent project loaded from repository:groupId:parent:pom:1.0.3[DEBUG] Parent project loaded ...[DEBUG] Skipped site descriptor for locale en[DEBUG] Skipped remote site descriptor check[WARNING] Unable to find a URL to the parent project. The parent menuwill NOT be added.[DEBUG] Attempting to load module information from local filesystem[DEBUG] Verifying availabilityof /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom from [central (http://repo1.maven.org/maven2, releases)][DEBUG] Skipped remote update check forgroupId:parent:pom:1.0.3, locally cached artifactup-to-date.[DEBUG] Using connector WagonRepositoryConnector with priority 0 forhttp://repo1.maven.org/maven2Downloading:http://repo1.maven.org/maven2/groupId/parent/1.0.3/parent-1.0.3.pom[DEBUG] Reading resolution trackingfile /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-1.0.3.pom.lastUpdated[DEBUG] Writing resolution trackingfile /home/agomes/.m2/repository/groupId/parent/1.0.3/parent-
1.0.3.p
om.lastUpdated[INFO]------------------------------------------------------------------------[INFO] Reactor Summary:[INFO] [INFO] projectName .............................................. FAILURE[12.552s][INFO] moduleA ........................................ SKIPPED[INFO] moduleB ....................................... SKIPPED[INFO] moduleC ................................ SKIPPED[INFO] moduleD ........................... SKIPPED[INFO] moduleE .......................................... SKIPPED[INFO] moduleF ................................... SKIPPED[INFO]------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO]------------------------------------------------------------------------[INFO] Total time: 13.045s[INFO] Finished at: Tue Oct 30 18:39:43 WET 2012[INFO] Final Memory: 26M/247M[INFO]------------------------------------------------------------------------[ERROR] Failed to execute goalorg.apache.maven.plugins:maven-site-plugin:3.
1:site (
default-site) onproject projectName: SiteToolException: Unable to read local module-POM: 1problem was encountered while building the effective model forgroupId:moduleA:1.1.5-SNAPSHOT[ERROR] [FATAL] Non-resolvable parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2) @groupId:projectName:1.1.5-SNAPSHOT, /home/agomes/workspace/projectName/pom.xml,line 9, column 10[ERROR] for project groupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml for projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml[ERROR] -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed toexecute goal org.apache.maven.plugins:maven-site-plugin:3.1:site(default-site) on project projectName: SiteToolException: Unable to read localmodule-POMatorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)atorg.apache.maven.lifecy
cle.inte
rnal.MojoExecutor.execute(MojoExecutor.java:153)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)atorg.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)atorg.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)atorg.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.Deleg
atingMet
hodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:616)atorg.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)atorg.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)atorg.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused by: org.apache.maven.plugin.MojoExecutionException:SiteToolException: Unable to read local module-POMatorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:300)atorg.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)atorg.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)atorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)... 19
moreCaus
ed by: org.apache.maven.doxia.tools.SiteToolException: Unable toread local module-POMatorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:892)atorg.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)atorg.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:293)... 23 moreCaused by: org.apache.maven.project.InvalidProjectModelException: 1problem was encountered while building the effective model forgroupId:moduleA:1.1.5-SNAPSHOT[FATAL] Non-resolvable parent POM forgroupId:projectName:1.1.5-SNAPSHOT: Could not find artifactgroupId:parent:pom:1.0.3 in central(http://repo1.maven.org/maven2) @groupId:projectName:1.1.5-SNAPSHOT, /home/agomes/workspace/projectName/pom.xml,line 9, column 10for project groupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectName/moduleA/pom.xml for projectgroupId:moduleA:1.1.5-SNAPSHOTat /home/agomes/workspace/projectNa
me/modul
eA/pom.xmlatorg.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:194)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:211)atorg.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:223)atorg.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:888)... 25 more
>
>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven site can not find parent
Posted by mriss <ma...@gmail.com>.
I am having the same error here, but no clue on the cause.
Marcelo
--
View this message in context: http://maven.40175.n5.nabble.com/Maven-site-can-not-find-parent-tp5729099p5730240.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org