wt., 13 cze 2023 o 11:17 Guillaume Nodet <gno...@apache.org> napisał(a):
> I was assuming that the impact would be lowered by the fact that it's a > *Maven* parent, so it is kinda used *internally*. > But no problem on my side to revert this change for some time. > > I see that most of Maven plugins / shared components override plexus-utils version - so maybe it is not needed at all. As Guillaume writes, and the fact that the project overrides this version I agree that impact is small and only for Maven internal projects. We can think about improvements - taking into account the above I would like to process this release to the end. > Le mar. 13 juin 2023 à 10:58, Elliotte Rusty Harold <elh...@ibiblio.org> a > écrit : > > > It's not that these problems are unsolvable. They're not. But > > splitting the packages like this means that a lot of projects are > > going to burn a lot of hours working around unexpected breakages. It's > > annoying for someone who's well-versed in BOMs, dependency management, > > classpath loaders, exclusions, and the Maven dependency resolution > > algorithm. It's much worse for anyone who isn't hip deep in this muck > > on a day-to-day basis. I worry this is going to cause a lot of tsuris > > for no particular benefit. > > > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > ------------------------ > Guillaume Nodet > -- Sławomir Jaranowski
