THE GENERAL CASE
I agree that dependsOn should continue to require success of the
pre-requisites. I think the awkwardness is due to the fact that tasks that
perform some kind of check (like test tasks) have two levels of
success/failure:
1) the check was/was not executed successfully
2) the chec
I'm not sure we want to water down the strict meaning of 'dependsOn':
"A.dependsOn(B)" means that A cannot start executing until B has
successfully completed executing. I'd rather add more kinds of dependency
relationships if required, rather than water down this contract.
In this case TestReport
This seems like a valid use case to me as well. Should we simply not skip
the execution of a finalizer task if its finalized task on which it also
depends fails? It shouldn't be hard to implement, I can have a look if you
guys want me to.
On Sun, Feb 16, 2014 at 11:20 AM, Perryn Fowler <
perryn.f
In fact, that user was trying to use a TestReport task to reportOn a Test
task. Doing that automatically adds a dependency on the Test task from the
TestReport task. In turn that means that Test.finalizedBy(TestReport) will
not work properly.
That seems unfortunate since a test report is one of th
someone else trying to do the same thing...
http://forums.gradle.org/gradle/topics/finalizer_task_does_not_run_if_finalized_task_fails
On Mon, Jan 20, 2014 at 10:25 PM, Luke Daley wrote:
> Hi,
>
>
> http://forums.gradle.org/gradle/topics/finalizer_tasks_that_depend_on_the_base_task_do_not_exec