Re: Question regarding repository overriding.

On Thursday, 15 December 2016, Christian Schulte wrote: > Am 12/15/16 um 01:09 schrieb Christian Schulte: > > I would have expected the nearest wins strategy as well, BTW. Seems to > > not make sense for the resolver to just ignore repository declarations > > matching an ID

Re: Question regarding repository overriding.

Am 12/15/16 um 01:09 schrieb Christian Schulte: > I would have expected the nearest wins strategy as well, BTW. Seems to > not make sense for the resolver to just ignore repository declarations > matching an ID already discovered at another level. Well. Makes perfect sense for the resolver to do

Re: Question regarding repository overriding.

I would have expected the nearest wins strategy as well, BTW. Seems to not make sense for the resolver to just ignore repository declarations matching an ID already discovered at another level. - To unsubscribe, e-mail:

Re: Question regarding repository overriding.

Am 12/14/16 um 20:41 schrieb Stephen Connolly: > definition nearest to the project should win is the principle that has been > in force... That's what Maven core developers had in mind. Maven resolver developers did the opposite. See this class:

Re: 2nd question regarding repository overriding.

profiles are applied IMHO *after* the current pom... and whatever is in the current pom overrides dependencies... On 13 December 2016 at 01:57, Christian Schulte wrote: > Am 12/13/16 um 02:32 schrieb Christian Schulte: > > Consider these projects: > > > > P1 declares a

Re: Question regarding repository overriding.

definition nearest to the project should win is the principle that has been in force... when the definition is coming from a dependency, however, the concept of distance can become confused - especially given how the dependency graph is version conflict reduced On 13 December 2016 at 01:32,

2nd question regarding repository overriding.

Am 12/13/16 um 02:32 schrieb Christian Schulte: > Consider these projects: > > P1 declares a repository with id 'central' and a dependency on D1 > available in that repository. > > D1 declares a repository with id 'central' with a different URL and has > a dependency management import

Question regarding repository overriding.

Consider these projects: P1 declares a repository with id 'central' and a dependency on D1 available in that repository. D1 declares a repository with id 'central' with a different URL and has a dependency management import declaration on D2. When importing D2 into the effective model of D1,