Hi Chris, > ...but some naive google searching suggests it's possible to do something > similar using "apply from" to load in a *.gradle file using an arbitrary
Gradle is like ant (or more) -- you can do pretty much anything. So yes, you can load arbitrary config files. There are certain special properties which govern how gradle itself is launched though (like daemon forking rules) and I don't know if you can override these from the project-build level. These raise my concern a bit (especially the daemon forking property, which I don't want to override globally). > FWIW: I'm not sure if the deterministic ordering is that important -- I agree at this stage it may be not that important. > (i don't know that i've ever tried to rerun that exact list of every test > that ran in the same JVM in the same order as what was reported -- or even > how i would if i wanted to other then with a really fucking complicated > -Dtests.class=... param) The ant runner uses identical order (for that first batch of "hard-scheduled" test suites) if you pass it the same seed. This isn't that important I think. D. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
