On 14/09/2012, at 10:06 PM, Hans Dockter wrote: > > > On Fri, Sep 14, 2012 at 1:42 PM, Luke Daley <[email protected]> wrote: > Hi, > > Gradle 1.2 broke Cobertura support for at least two known ways of using > Cobertura with Gradle. A quick google found four different approaches to > using Cobertura with Gradle, and I suspect there are more out there. > > I'm wondering if we should pull support for this into core, under the same > grounds that caused us to pull check style support into core. That is, it's a > strategic advantage to have a working, capable, tested, documented solution > for code coverage. > > I think there is no question that we need a coverage solution in core. It is > something many projects obviously need. The reason why we haven't added it in > the earlier days was that it is a perfect candidate for initializer and > finalizer tasks. So my idea was always to have this a the first use case for > those enhancements. But I think we shouldn't wait for this to happen.
We really try to drive the planning with use cases these days. Cobertura support is a use case, finalisers are an implementation. If we think Cobertura support is important, then finalisers would get implemented. If we think Cobertura support is not important or doesn't end up needing finalisers, then finalisers will have to wait. We should be trying not to defer use cases because some implementation is not available (but it's all a trade-off). -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
