On 7 November 2011 22:26, Adam Murdoch <[email protected]> wrote:
> Hi,
>
> 1. Should the forced version be applied to the parent pom of a given pom?
> For example, if someGroup:someArtifact:1.2 declares a parent pom of
> someGroup:someParent:72, and we force someGroup:someParent:80, which
> version of someParent should be used?
>
> I would think we should use the parent declared in the pom in this
> instance.
>
> +1. I think parent POMs are different from dependencies in a "extends" vs
"uses" type of way. So the parent POM that is used is more fundamental to
the construction of the module, whereas dependencies are more about how the
module can be used.
> 2. Should you be able to specify a dynamic version for the forced version?
> Something like:
>
>
> configurations.compile.resolveStrategy.force("group:module:latest.integration")
>
> I would think you should be able to (and probably can at the moment). In
> which case we should change the type of ResolutionStrategy.forcedModules to
> be something other than ModuleIdentifier, probably a new interface called
> ModuleSelector.
>
Makes sense to me. In practice, I think people will expect this to work.
Daz
