{"push_id":1084428300,"size":1,"distinct_size":1,"ref":"refs/heads/0.6-branch","head":"6b004cf47a065bbcebbbd3ac0d6e00d767ded1ad","before":"bee0f7bbc7f0cc1ac2c4d0dbf9229103e6f8f7ea","commits":[{"sha":"6b004cf47a065bbcebbbd3ac0d6e00d767ded1ad","author":{"email":"d6b2a78430fa19c2268a9daed065d59fc3b5c20c@alumni.rice.edu","name":"Paul Holser"},"message":"Ensure ordering within a CompositeGenerator\n\nSome tests rely on the ordering of items that the ServiceLoader emits.\nThe Maven plugin we use to generate the ServiceLoader provider config\nfiles for generators cannot, and should not, enforce any particular\nordering of the contents of the generated files. Therefore, this change\nenforces an ordering by class FQN of the generators fed to a\nCompositeGenerator.\n\nThis problem became apparent when some tests failed unexpectedly on\nTravis CI. We then discovered our tacit dependency on ordering within a\nServiceLoader provider config file.","distinct":true,"url":"https://api.github.com/repos/pholser/junit-quickcheck/commits/6b004cf47a065bbcebbbd3ac0d6e00d767ded1ad"}]}