[ http://jira.codehaus.org/browse/CONTINUUM-549?page=comments#action_73503 ] Brill Pappin commented on CONTINUUM-549: ----------------------------------------
I originally agreed with the comments from Jamie Flournoy, Henri Yandell, Trygve Laugstol but after using it for a while I have changed my mind. The reason is that there are many things that can cause a build to fail including dependency issues, build order, environment (e.g. systems bounces the cvs server) etc. and in those cases you *do not* want to change the code in the module thats failing because its dependency is failing. I've run into all of those mentioned in the last few weeks and it's a bit of a pain to have to go and "force" build the module. The only way to be sure that a build reruns if it fails is to run it even if there are no changes. If you don't have this ability then you have to manually go an force a build when it not actualy required. So IMO, Christian Gruber has the best idea -- make it configurable. > A build must always be executed when previous was in failure even if there > are no changes in scm > ------------------------------------------------------------------------------------------------ > > Key: CONTINUUM-549 > URL: http://jira.codehaus.org/browse/CONTINUUM-549 > Project: Continuum > Issue Type: Improvement > Components: Core system > Affects Versions: 1.0.2 > Reporter: Emmanuel Venisse > Fix For: 1.1 > > -- 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
