I love the idea of bringing some great tools to ASF: happy of this discussion
each one will require a separate in-depth evaluation of what it would mean to have some part available as default in Maven CLI distribution vs what would remain as a plugin or stil remain an extension I personally studied a little bit njord: I feel in this case that there is a good opportunity, that will require to concretely describe what it would bring I still need to better understand code, and how I would personally imagine maintain it I think this is what we'll require for each cited component: go from great experience from a few users to something that we clearly position in the Maven codebase and maintenance overview On 2025/07/22 09:22:16 Tamás Cservenák 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
