Cool it works.

Well, yes, all this comes from a "lab" located at small corner of Jylland :D
Unsure many are aware of these things, I did not publicize them yet.
I just like to play with them.

Regarding direct dependencies:
I am a member of a school that teaches that a tool should never
override user input :)
(extreme example: like have a terminal where you type "ls" and it does
"oh, I know better what you want" and executes "cd" instead)

In other words, IF a user has a POM that states dep 1.1 (so is a
direct dependency), Maven should _never_ come up with a classpath for
that POM having dep 1.2 only as it "fits better". If needed, it should
FAIL the build instead (more about that later, another upcoming
feature of resolver), and let the user do his homework. I don't buy
this "once upon time" story, as that clearly means that you are not
gardening well in your own garden :D Users should do their homework,
and not just "throwing deps onto projects" (even worse, by some
automaton like dependabot) and expect tooling will sort it out...

T

On Thu, Oct 23, 2025 at 11:39 AM Vladimir Sitnikov
<[email protected]> wrote:
>
> Great. Many thanks.
> Nice, now I get it working.
>
> >Again, all this is experimental
>
> Are there any plans making selectionStrategy=highest skipper=versioned the
> new default?
> I found no issues/discussions regarding the defaults.
>
> -----
>
> Looks like selectionStrategy=highest skipper=versioned does not overcome
> "direct dependency" version.
>
> What is the reason to enforce the version of a direct dependency in that
> case?
>
> The use case is as follows:
> a) once upon a time the application added Guice, and it used 3.0
> b) later, a library was added to a dependency, and the library happens to
> require Guice 5.0
>
> In that case, Maven enforces 3.0 which causes runtime failures even with
> highest+versioned mode.
> WDYT?
>
> Vladimir

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to