Hans, On Mon, 2008-09-01 at 05:23 +0200, Hans Dockter wrote: > On Aug 31, 2008, at 8:52 AM, Russel Winder wrote: > > > There is currently a lot of chatter about hierarchy configuration. I > > would like to re-poke GRADLE-27 which is about doing something > > about the > > diktat that JUnit is the only supported unit test framework since this > > is more of a blocker to use of Gradle for me that the hierarchy > > structure. > > It is easy to use TestNg with Gradle via its Ant task. This is not as > convenient as having it as part of our Java plugin but nobody is > blocked from using TestNG when using the current version of Gradle.
I think this is the wrong position to take. If I have to start constructing my own lifecycle framework because the standard one is insufficiently parameterized and yet I have a standard lifecycle project, then the Gradle realization of convention over configuration has failed me. Alternatively you need to advertise that Gradle supports only the inferior JUnit and discriminates against the superior TestNG. If you think the solution is easy, perhaps you can convince me by showing me what sort of code I should have in my build.gradle file? -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
