> > It's the other way around. I believe things currently work the way we > want, and we'd have to add extra code to allow you to force the parent pom. > I think we just need an integration test to make sure this is the case, and > to lock it down until a use-case comes along. >
In that case it makes perfect sense. I'll make sure we have coverage for it. > It's not the actual forced version. It's a selector, or set of criteria, > for the version or versions we should consider for a given module. We may > extend this to include criteria on attributes other than version: for > example, 'only consider released versions', or 'only consider those > architectures which are compatible with the current platform'. The > generalisation is required right now, as ExternalDependency also is-a (or > has-a) one of these things. I would call it something like a > ModuleVersionSelector to reflect what it actually is. > ModuleVersionSelector works for me. I'll make some changes to accommodate that. > We need coverage either way: if we support it, we need an int test that > shows it works. If not, we need an int test that shows you get a nice error > message when you accidentally use a dynamic version. > I like the idea, especially 'nice error message' :) Cheers! -- Szczepan Faber Principal engineer@gradleware Lead@mockito
