maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "werner mueller (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-271) perform goal sometimes fails with multi-module projects
Date Thu, 16 Aug 2007 16:16:47 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105025
] 

werner mueller commented on MRELEASE-271:
-----------------------------------------

hallo

today the very same thing happened here too. the same parent-pom and release was running before.
i did move it in subversion and updated the scm connection settings.

the release:perform goal fails while it tries to find a dependency it is supposed to create.

the mentioned workaround in maven.users list:
$ mvn release:prepare -DpreparationGoals="clean install"

solves this issue so i can release again. but well it is kinda weird this came out of nowhere.



> perform goal sometimes fails with multi-module projects
> -------------------------------------------------------
>
>                 Key: MRELEASE-271
>                 URL: http://jira.codehaus.org/browse/MRELEASE-271
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4, 2.0-beta-6
>         Environment: XP
>            Reporter: David Hoffer
>         Attachments: MavenReleaseFailure.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 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

        

Mime
View raw message