On Tue, 2010-04-06 at 12:47 +1000, Adam Murdoch wrote: > How so? It's got unit tests in src/test/java, and integration tests in > src/integration-test/java. The integration tests have a separate compile > and runtime classpath, which inherit from the unit test compile and > runtime classpaths, which inherit from the production compile and > runtime classpaths. What more do you need?
Examples of use in the documentation? A chapter devoted to this in the user manual? Or at least a section in the Java and Groovy plugin chapters. Currently the string integration-test does not appear in the user guide at all. Outstanding questions: How does the user access this phase from the command line? What are the task dependencies? Why doesn't the Gradle build use this? What is the way of configuring this task in the build.gradle file? How do I use this functionality that I had no idea existed? Why is the example in the source code empty? Is 0.9 really ready without this information available? Will the feature change radically between now and the next snapshot release? Is reading and understanding the course code the only way of finding things out? There is more but that is grumpy enough for one morning :-) -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
