Howdy, Toolbox is very Maven 3 focused, it relies on MIMA that is still Maven 3 / Resolver 1. Toolbox is not related to Maven 4 at all, unsure from where you got this conclusion from. Yes, Toolbox is there as "cook book", fixes multiple issues, among other things this issue as well: https://maven.apache.org/resolver/common-misconceptions.html
HTH T On Fri, 19 Jun 2026 at 09:13, hitesh sai <[email protected]> wrote: > > Hi Maarten, Tamás, and Gary, > > Thanks for the toolbox references—I hadn't seen those before. > and they're incredibly helpful. I can see that toolbox:tree-find > already solves the core problem I identified. > > A few thoughts: > > 1. **Maven 4 vs Maven 3 gap**: Toolbox appears to be Maven 4 > focused. My proposal could target Maven 3.x users who don't > have access to these tools yet. The maven-dependency-plugin > works across both major versions. > > 2. **Integration vs. standalone**: Rather than a separate toolbox > plugin, embedding this functionality directly into > maven-dependency-plugin (as dependency:insight) would make it > more discoverable for users running `mvn dependency:<tab>`. > > 3. **Learn from toolbox's approach**: I'd be interested in how > toolbox implements tree-find (the artifact matching DSL, > performance on large graphs) and adapt those lessons for the > dependency plugin. > > Given what you've shown me, I'm now wondering if this should be > positioned as: > - A backport of toolbox's tree-find to Maven 3.x via the > dependency plugin, OR > - A focus on integration with MPH-183 (help-plugin) as Maarten > suggested, to complement help:effective-pom > > I'm flexible on direction. What would be most valuable for the > community? > > Thanks, > Hitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
