> On 09/10/2011, at 10:39 PM, Hans Dockter wrote: > >> A common use case in Gradle is that you want to have different >> variations of task behavior. Our goal is in general to avoid the use >> of multiple actions per task to achieve this. In any case, let's look >> at an example for variations: You want a test task that runs with and >> without coverage. This variation does often not affect the behavior of >> the executed task but rather the wiring. > > Why would you want to run the tests without coverage?
I've had scenarios where the instrumented classes would not run without the coverage jar file being on the classpath (I don't remember the details, though). Shipping the coverage jar file with my production bundle is of course not an option. Etienne -- View this message in context: http://gradle.1045684.n5.nabble.com/Task-Variations-tp4884963p4893543.html Sent from the gradle-dev mailing list archive at Nabble.com.
