Author: vmassol
Date: Tue Aug 22 07:56:19 2006
New Revision: 433653
URL: http://svn.apache.org/viewvc?rev=433653&view=rev
Log:
MCLOVER-50: Test failure during Site goal should not stop the Clover build
Modified:
maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml
Modified:
maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml?rev=433653&r1=433652&r2=433653&view=diff
==============================================================================
---
maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml
(original)
+++
maven/plugins/trunk/maven-clover-plugin/src/main/resources/META-INF/maven/lifecycle.xml
Tue Aug 22 07:56:19 2006
@@ -16,6 +16,27 @@
</execution>
</executions>
</phase>
+
+ <!-- This below is a HACK. It tries to prevent the build from stopping in
+ case of build failures as we could still like to generate Clover
+ reports even if it happens. The Clover plugin cannot know about all
+ plugins that can execute and fail the build and moreover which can
be
+ bound to any phase by the user. A better solution would be for Maven
+ to have a flag that says "continue the build even in case of
+ failures". -->
+ <phase>
+ <id>test</id>
+ <configuration>
+ <testFailureIgnore>true</testFailureIgnore>
+ </configuration>
+ </phase>
+ <phase>
+ <id>integration-test</id>
+ <configuration>
+ <testFailureIgnore>true</testFailureIgnore>
+ </configuration>
+ </phase>
+
</phases>
</lifecycle>
</lifecycles>
