[
http://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159677#action_159677
]
Benjamin Bentmann commented on MRELEASE-271:
--------------------------------------------
bq. This behaviour is back when using the release plugin in tandem with
maven-javadoc-plugin 2.5.
Owen, can you be more specific about the exact point of the build that fails,
maybe provide a log? For instance, does it fail during the site generation or
during the normal build?
My guess is that is breaks during the site generation. If so, have you tried to
exclude the new {{javadoc:*aggregate}} mojos introduced in version 2.5 of the
Javadoc plugin as outlined in [Selective Javadocs
Reports|http://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-javadocs-report.html]?
> 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
> Components: prepare
> 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
