[
http://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257733#action_257733
]
Marcin Kuthan commented on MRELEASE-271:
----------------------------------------
I read blog post
http://www.sonatype.com/people/2010/12/whats-in-maven-3-0-for-users/, and
Benjamin said that Maven 3.x is not affected by this bug. I removed
{code}
<preparationGoals>clean install</preparationGoals>
{code}
from my pom, and perform release with Maven 3.0.2. And build failed :-(
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on
project modular-war-parent: failed to get Reports: Failed to execute goal on
project modular-war-webapp: Could not resolve dependencies for project
com.googlecode.m4enterprise:modular-war-webapp:war:0.0.11: Could not find
artifact com.googlecode.m4enterprise:modular-war-core:jar:0.0.11 in
roche-releases-new
{code}
Perhaps it is a bug in the site plugin not in the Maven core, but I still have
to use clean install as release preparation goals.
----
Marcin
m4enterprise.googlecode.com
----
> 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, 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 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
