Hi,
I'm working on the clover plugin and I'd like to ensure any failing test
does not stop the build. Of course this should work independently to which
phase the user has attached the surefire plugin to. Right now I've added the
following to cargo's lifecycle.xml file:
<lifecycles>
<lifecycle>
<id>clover</id>
[...]
<phase>
<id>test</id>
<configuration>
<testFailureIgnore>true</testFailureIgnore>
</configuration>
</phase>
<phase>
<id>integration-test</id>
<configuration>
<testFailureIgnore>true</testFailureIgnore>
</configuration>
</phase>
</phases>
</lifecycle>
</lifecycles>
As you can this is not optimal for 2 reasons:
1) It covers only 2 phases and if the user decides to bind the surefire
plugin to another phase it won't work. Or I'll need to add the
testFailureIgnore configuration for all possible phases.
2) The testFailureIgnore property is not namespaced. If some other plugin
have the same property it'll impact it.
Are there ways to solve 1) and 2)?
Thanks a lot
-Vincent
p5.vert.ukl.yahoo.com uncompressed Tue Aug 22 14:27:00 GMT 2006
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet
!
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos
expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
