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

Michael Osipov closed MRELEASE-271.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> perform goal sometimes fails with multi-module projects
> -------------------------------------------------------
>
>                 Key: MRELEASE-271
>                 URL: https://issues.apache.org/jira/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
>            Priority: Major
>         Attachments: MavenReleaseFailure.zip, SuccessfulReleaseBuild.txt, 
> release.zip
>
>
> 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
(v7.6.3#76005)

Reply via email to