Hi Russel, I don't know the answers to your questions, on the contrary I'd like to ask you one. :)
> I am increasingly of the view that this way of compiling and running the > tests is the wrong way of doing things -- even for unit tests. I think > the artifact should be made and the tests compiled and run against that. Could you explain what would be the benefit of this ? Could you give an example when such testing is able to reveal more bugs then the testing done on the compiled classes dir ? -- best regards Tomek Kaczanowski http://kaczanowscy.pl/tomek > From what I can see Maven is not able to do this sort of testing. OK > there is an integration-test phase but the directory of compiled code is > always in the classpath of the test compile and execution, which > effectively ruins any idea of running the unit tests with the jar > instead of the directory of compiled classes. > > I am hoping that this restriction has not been bolted into Gradle. > > So I want to: > > compile the classes of the jar > create the jar > compile the tests using the jar and not the directory of compiled > classes > run the tests using the jar and not the directory of compiled classes. > > Is there a Gradle idiom/example for doing this? > > Thanks. > > BTW Is gradle heading towards Maven's ability to generate websites with > all the various reports? That is a very cool feature of Maven. > > -- > Russel. > ============================================================================= > Dr Russel Winder Partner > xmpp: [email protected] > Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 > 41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected] > London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
