Am 12/24/16 um 17:59 schrieb Hervé BOUTEMY: > +1 > > notice that it may show that we have an issue with the way transitivity + > nearest resolution are applied > > IIUC this case, we have: > 1. a direct dependency with scope = test > 2. a transitive dependency with scope = compile > > the result can't be just the direct dependency with scope=test: scope of > direct dependency has to switch to compile (and I don't know which version > should be kept: direct or transitive)
Following the nearest node wins strategy, current master does exactly what is expected. Adding a test scope dependency to a POM that is already part of the test classpath just means that someone just did not notice the dependency already is available to that scope due to other reasons and that a scope is being overridden that way (by pulling it nearer and overriding the scope). Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
