Re: Fwd: [GSoC 2027] Proposal idea: dependency:insig ht — tracing why an artifact is on the classpath

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