You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Georges-Etienne Legendre (JIRA)" <ji...@codehaus.org> on 2010/05/26 14:24:12 UTC
[jira] Commented: (MNG-4687) Maven should not warn about incorrect
parent path when no relativePath is specified
[ http://jira.codehaus.org/browse/MNG-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222725#action_222725 ]
Georges-Etienne Legendre commented on MNG-4687:
-----------------------------------------------
Also,
The release plugin doesn't like empty relativePath. It still works, but we get strange exceptions in the log:
[INFO] ------------------------------------------------------------------------
[INFO] Building XYZ Parent POM 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] maven-release-plugin:2.0:prepare (default-cli) @ xyz-parent
...
[INFO] Transforming 'XYZ Parent POM'...
org.apache.maven.project.ProjectBuildingException: Error resolving project artifact: Missing:
----------
1) com.xyz.maven.pom:xyz-parent:pom:RELEASE
----------
1 required artifact is missing.
for artifact:
com.xyz.maven.pom:xyz-parent:pom:RELEASE
from the specified remote repositories:
nexus (https://xyz/devel/nexus/content/groups/public, releases=true, snapshots=false)
for project com.xyz.maven.pom:xyz-parent:pom:RELEASE
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:237)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:204)
at org.apache.maven.project.MavenProject.getParent(MavenProject.java:351)
at org.apache.maven.project.MavenProject.hasParent(MavenProject.java:370)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.rewriteParent(AbstractRewritePomsPhase.java:393)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:249)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:208)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:114)
at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.simulate(AbstractRewritePomsPhase.java:780)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:199)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
----------
1) com.xyz.maven.pom:xyz-parent:pom:RELEASE
----------
1 required artifact is missing.
for artifact:
com.xyz.maven.pom:xyz-parent:pom:RELEASE
from the specified remote repositories:
nexus (https://xyz/devel/nexus/content/groups/public, releases=true, snapshots=false)
at org.apache.maven.artifact.resolver.DefaultResolutionErrorHandler.throwErrors(DefaultResolutionErrorHandler.java:71)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:233)
... 34 more
[INFO] Not removing release POMs
[INFO] Full run would be checking in 1 files with message: '[maven-release-plugin] prepare for next development iteration'
[INFO] Release preparation simulation complete.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.891s
[INFO] Finished at: Wed May 26 08:04:02 EDT 2010
[INFO] Final Memory: 4M/8M
[INFO] ------------------------------------------------------------------------
> Maven should not warn about incorrect parent path when no relativePath is specified
> -----------------------------------------------------------------------------------
>
> Key: MNG-4687
> URL: http://jira.codehaus.org/browse/MNG-4687
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 3.0-beta-1
> Reporter: Paul Gier
> Priority: Minor
> Attachments: MNG-relativePath.zip
>
>
> If a module pom uses a parent other than the one in the parent directory, maven logs a warning. In some cases it is necessary that a module pom has an external parent pom, and there is no way to refer to this external pom in the relativePath. If nothing is specified in the relativePath, Maven should not log the warning.
> {noformat}
> [WARNING] 'parent.relativePath' of POM org.maven.test:relative-path-parent:0.0.1-SNAPSHOT (/home/pgier/projects/MNG-relativePath/module-1/pom.xml) points at org.maven.test:relative-path-test instead of org.apache.maven:maven-parent, please verify your project structure @
> {noformat}
> The attached zip reproduces the warning.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira