You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2008/03/18 15:11:48 UTC
[jira] Commented: (MRELEASE-271) perform goal sometimes fails with
multi-module projects
[ http://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127747 ]
Brian Fox commented on MRELEASE-271:
------------------------------------
I think the root cause of this problem is the javadoc 2.3 started forking lifecycles. This will start a new build at each child and that particular build doesn't know about all the siblings so the dependency lookup fails. I think if you look closely at the logs, you'll see that it's the forked build failing and not the main one. Fortunately, Javadoc 2.4 is released which reverts to the 2.2 behavior and we recommend everyone update to it. Please try it and add a comment if it helps you or not.
> 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