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 <c...@schulte.it> wrote: > 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 declaration on D2. > > > > When importing D2 into the effective model of D1, which repository > > should be used? Does the 'central' repository definition in D1 override > > the 'central' repository definition in P1? How would you expect Maven to > > behave? > > > > Regards, > > > > What repository to use if there is an active profile in the settings > also declaring a 'central' repository? That's the IT currently failing. > The resolver does not know about those profiles. Maybe that's the real > issue to fix. So - when there is an active profile in the settings > declaring a 'central' repository does that profile need to get injected > everywhere (also when building effective models of dependencies) or does > that profile only need to get injected into the initial effective model > and then can get ignored when building dependencies? > > <https://issues.apache.org/jira/browse/MNG-4347> > <https://issues.apache.org/jira/browse/MNG-5639> > > The fix to MNG-5639 introduced the issue uncovered now. > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
