https://the-asf.slack.com/ , no more sure how invites work these days but can have a look next week
Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin) Le jeu. 25 juin 2026 à 09:19, hitesh sai <[email protected]> a écrit : > Hi Romain, > > That makes sense now. Maveniverse already covers the Resolver side, > so the real work is the new Maven 4 API for packaging plugins to > report their dependency decisions, with WAR plugin as the MVP. > > I'll study the Maveniverse/Toolbox codebase to understand what's > already available before designing the plugin API layer. > > Which Slack workspace should I join for further discussion? > > Thanks, > Hitesh > > On Thu, 25 Jun 2026 at 12:39, Romain Manni-Bucau <[email protected]> > wrote: > > > Hi Hitesh > > > > Collector listener can be a starting point to get something into motion > but > > I think the solution should be maven 4 focused because it needs a new api > > where the war plugin will say "i used dependencies from project.artifacts > > with these custom exclusions and additional jars" (warexcludes and war > > overlay cases as examples). > > > > In maven 3 there is not maven plugin api so can be hard to do cleanly - > in > > particular "now" we move to maven 4. > > > > For the question 1, maveniverse plugin does the job so once you add the > api > > insights you can do a report by packaging plugin (plugin bundling an > > archive, dont mix it with maven packaging meaning). > > > > Hope it makes sense, will be in slack next week if it helps > > > > > > Romain Manni-Bucau > > @rmannibucau <https://x.com/rmannibucau> | .NET Blog > > <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/ > > > > | Old > > Blog <http://rmannibucau.wordpress.com> | Github > > <https://github.com/rmannibucau> | LinkedIn > > <https://www.linkedin.com/in/rmannibucau> | Book > > < > > > https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064 > > > > > Javaccino founder (Java/.NET service - contact via linkedin) > > > > Le jeu. 25 juin 2026, 08:27, hitesh sai <[email protected]> a écrit > : > > > > > Hi Romain and Tamás, > > > > > > Two quick technical questions before I go deeper: > > > > > > 1. For capturing Resolver decisions (version mediation, conflict > > > resolution) — is DependencyCollectorListener the right hook > > > point, or is there a better API in Maven Resolver for the > > > Transform step specifically? > > > > > > 2. For WAR plugin instrumentation on Maven 3.x — is a lifecycle > > > listener the right approach, or is there a cleaner extension > > > point you'd recommend? > > > > > > Thanks, > > > Hitesh > > > > > > On Sat, 20 Jun 2026 at 16:36, hitesh sai <[email protected]> > wrote: > > > > > > > Hi everyone, > > > > > > > > Thank you for the guidance and support these past few days. Your > > > > feedback shaped this idea into something real—and having Mr. Romain > > > > as a mentor is incredible. > > > > > > > > I'm excited to build this tool and contribute to Maven. Feel free to > > > > reach out if you'd like to discuss anything—I'm available on the > > > > mailing list or you can DM me on GitHub. > > > > > > > > See you in the code! > > > > > > > > Best regards, > > > > Hitesh Sai > > > > GitHub: Hiteshsai007 > > > > > > > > > >
