[jira] (MRELEASE-271) perform goal sometimes fails with multi-module projects

["Jesse Glick (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348274#comment-348274 ] 

Jesse Glick commented on MRELEASE-271:
--------------------------------------

Maven 3.1.0 still seems to be affected. Just have a multimodule project where the parent POM and all modules share the same version (and depend on one another using {{$\{project.version}}}), using {{maven-release-plugin 2.5}}. Unless I specify {{<preparationGoals>clean install</preparationGoals>}} the build fails in {{release:prepare}} on the second module, since it had only run the {{verify}} goal on the first module and so it tried to download the release version of the first module from the remote repository which of course failed. Possibly this is because I am using {{<packaging>hpi</packaging>}} (Jenkins plugins) and so it could not find the first module?s final build product in the reactor.

> perform goal sometimes fails with multi-module projects
> -------------------------------------------------------
>
>                 Key: MRELEASE-271
>                 URL: https://jira.codehaus.org/browse/MRELEASE-271
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-4, 2.0-beta-6
>         Environment: XP
>            Reporter: David Hoffer
>         Attachments: MavenReleaseFailure.zip, release.zip, SuccessfulReleaseBuild.txt
>
>
> We have a multi-module maven project that has recently started failing in the release:perform goal.  
> We have just added a couple more modules but do not know if that is the cause of the failure.  It seems that the release:perform fails to compile the source after the SCM tag and checkout.  The failure says that it cannot find a dependent jar but it is that jar that it is supposed to be building and releasing!  I updated to use the latest 2.0-beta-6 release plugin version but this did not help. 
> Upon receiving feedback in the maven users group that others have seen this behavior I followed their advise and added <configuration> <preparationGoals>clean install</preparationGoals></configuration> to my parent pom which did fix the problem.
> Why is the release goal failing now?  When do I and when do I not need these changes to my pom?  I will attach pom and build logs in hopes this can be fixed soon, let me know if you need additional information.
> -Dave



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