You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:50:08 UTC

[jira] (MRELEASE-646) release:prepare failed on parent's pom not localized in ../

     [ https://jira.codehaus.org/browse/MRELEASE-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-646.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> release:prepare failed on parent's pom not localized in ../
> -----------------------------------------------------------
>
>                 Key: MRELEASE-646
>                 URL: https://jira.codehaus.org/browse/MRELEASE-646
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>         Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> OS name: "windows 2003", version: "5.2", arch: "x86", family: "windows"
>            Reporter: amber
>
> Since Maven 3.x, the plugin failed during the prepare phase because of the "relativePath" error :
> Structure is :
> super-pom
>  |__foo1
>     |__foo2
>  |__foo3
>     |__foo4
> Foo1 is parent of foo3 but the plugin can't find it :
>  
> [INFO] Not generating release POMs
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for th
> is MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [ERROR] The build could not read 1 project -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR]   The project com.mycompany.testRelease.foo3:foo3:0.0.2 (C:\dev\test-rele
> aseplugin\foo3\pom.xml) has 1 error
> [INFO] [ERROR]     Non-resolvable parent POM: Failure to find com.mycompany.testRelease:
> foo1:pom:0.0.2 in http://localhost:8081/nexus/content/groups/public was cached in the local reposito
> ry, resolution will not be reattempted until the update interval of nexus has elapsed or updates are
>  forced and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> Here the foo3's pom :
> <parent>
>   <groupId>com.mycompany.testRelease</groupId>
>   <artifactId>foo1</artifactId>
>   <version>0.0.2</version>
> </parent>
> This pom was working fine with Maven 2.2.1 ans a mvn install command with Maven 3.x (just a warning about parent.path but Maven find the artifact into the local referentiel)
> Now I have to put relativePath :
> <parent>
>   <groupId>com.mycompany.testRelease</groupId>
>   <artifactId>foo1</artifactId>
>   <version>0.0.2</version>
>   <relativePath>../foo1/pom.xml</relativePath>
> </parent>
> and all works!
> it's not a real workaround because I use my project to generate an archetype, so I have to put the relativePath for the release plugin and remove it to create the archetype :(



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)