Howdy,

There are many things worth doing, and many are upcoming as well.
As part of Maven 4 work, Guillaume started building various projects
just to check how Maven 4 behaves.
One of the important changes in Maven 4 is "transitive dependency
manager" (also in upcoming 3.10.x but not enabled by default).

With it in play, there is an interesting question (for example sake,
stick to the version only): "why is this dependency version V1?"

I recorded the issue here as this
https://github.com/maveniverse/toolbox/issues/408

So, a mojo could:
- find a path from root to wanted/asked GAV
- would "walk" the path and get DM for node
- looking into DM and show matches -> display to user
- until it arrive to GAV

(as one DM could manage scope, other could manage version, etc)

So, this is just one idea.

Thanks
T


On Fri, 19 Jun 2026 at 17:03, hitesh sai <[email protected]> wrote:
>
> Hi Maarten, Tamás, and Gary,
>
> Thank you for the guidance on the toolbox and the resolver documentation.
> After reading through the common misconceptions page and "How Resolver
> Works," I better understand how conflict resolution happens in the
> Transform step.
>
> I'm now wondering: is the gap I'm trying to address actually worth solving?
>
> Currently, to see *why* a version was selected, users have to parse
> `mvn dependency:tree -Dverbose` output. But I realize now that this
> information — which versions were considered, which won, and why — is
> already computed by Resolver during conflict resolution.
>
> My question: Would it be valuable to expose this more cleanly through
> maven-dependency-plugin (say, `dependency:insight`), or would that
> duplicate what users can already do with `dependency:tree -Dverbose`
> and toolbox?
>
> I want to make sure I'm not proposing something that's already solved
> or outside Maven's scope before investing time in a detailed proposal.
>
> Thanks,
> Hitesh

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

Reply via email to