Allow changing defaults for @Property

[csamak]

There should be a way to change the default for @Property annotations so it doesn't always have to be done per-method. "Aggregating configuration" doesn't work in part because @Property can only be applied to methods, and I don't see another way to change the settings.

For example, for projects with complex types the default shrink depth may not be sufficient for most properties.

[pholser]

@csamak Thanks for your interest in junit-quickcheck! Sounds like a great idea.

Any particular form you'd imagine the default to take? Attributes of a class-level annotation? Config file in well-known location/class path?

[csamak]

I think for consistency (so things "just work") the aggregating config method described here would be nice if possible.

On top of that, for my project I'd like something global (i.e. shrink timeouts will be the same for all classes). A new config file will work, but maybe there's an option that fits junit-quickcheck's existing model.

What do you think about a configuration provider users can register through the ServiceLoader, similar to generators? Or, is there any global setting precedent in JUnit?

[pholser]

Maybe #173 can help. For method-level annotations like @Property, search for annotations on method, deep-annotation search on any such annotations, then jump up to enclosing class, then the superclass/superinterface hierarchy? Maybe such as Spring does?