My build manages versions numbers automatically and so dependencies tend to expressed as a range. I’ve noticed the range is passed through to the POM as a range whereas I want to pass through (publish) the resolved dependency. Is there a mechanism in gradle I’m missing to achieve this? I can see there is a PomDependenciesConverter abstraction but it looks like it is not something I can override
Therefore it looks like I’ll need to use ‘pom#whenConfigured’ and then
walk through the dependencies on the pom - search for the corresponding project configuration
get the ResolvedConfiguration from that - match up the POM dependency with the resolved one - update the POM dependency version to match
Is there a better way?
IMO the default behaviour should be to realise a static set of dependencies when I do an install rather than pass through an unstable dependency. This is how ivy works in this case fwiw.