Well, I am fine with that, but I have to put some related notes about it: The Toolbox I did not mention on purpose, as it is a strange beast. Functionality wise, it was meant (by me) as "dependency plugin replacement", but it also serves as "showcase for MIMA usage", hence it works as Maven Plugin and also CLI (almost each Mojo is also a picocli command). Moreover, it is coded in a specific way: Mojos/Cli are "zero logic", as they literally just call into a "shared" module (which is a reusable module showcasing MIMA+Resolver use cases) without any Maven Plugin or CLI dependencies. Finally, Toolbox served also as an "experiment" for the Artifact Source/Sink abstraction and a mini DSL to express filters/matchers/mappers/whatevers. All those turned out very good, and I am happy with them, but it is totally opposite how Maven core plugins were usually done so far.
That said, "adding some goals" from Toolbox may not be as simple as one may think. Thanks T On Sun, Aug 10, 2025 at 2:56 PM Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > > +1 > > I see that some of the goals from > https://maveniverse.eu/docs/toolbox/plugin-documentation/plugin-info.html > > can be added or refreshed in dependency plugin, like tree and so on ... > https://maven.apache.org/plugins/maven-dependency-plugin/ > > On Tue, 22 Jul 2025 at 11:22, Tamás Cservenák <ta...@cservenak.net> wrote: > > > > Howdy, > > > > I'd like to start a discussion about ingesting some Maveniverse "skunk > > works" projects into Maven project, as they seems utterly useful and wanted > > (and are proven): > > > > Mimir - is currently an extension and provides global cache (solves same > > problem as split repository, but is not as invasive and is hence, fully > > compatible even in Maven3 land). It can be made part of resolver and could > > be always present (and configurable). The LAN cache publishing should be > > omitted, as it is really a niche feature, and can be built atop of it. > > > > Njord - suite of extension and plugin, solving the problem of publishing, > > among others publishing to Maven Central Portal but also local staging. > > This one cannot be made "resolver only", we need to tinker how to do it > > (simplest: keep it current form next to existing extensions like build > > cache is). Part of it could be made Resolver only, like local staging is > > and publishing can be built atop of it. > > > > Heimdall - an extension improving Resolvers built in Remote Repository > > Filtering, the code should be really just applied onto Resolver existing > > RRF classes. Hence, this can directly improve Resolver and be part of it. > > > > ----- > > > > IMO, these should go into Resolver2/Maven4 and offer OOTB experience, while > > Maven3 users could still use Maveniverse or any other existing tools. > > Basically the goal would be to enhance Maven4 capabilities but not leave > > Maven3 users abandoned either, and have them hopping from 3 to 4 to deal > > with known functionalities (coming from extension in former, or from core > > in latter). > > > > WDYT? > > > > Thanks > > T > > > > -- > Sławomir Jaranowski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
