Le mer. 15 oct. 2025 à 10:50, Vladimir Sitnikov <[email protected]> a écrit :
> >But existing projects, assume your project works with the version it > >resolves today, changing will obviously break > > It is far from obvious. It is not fair to say "just reverse and the issue > will reverse". > It does not work like that. > Please clarify the exact reason "Maven with the added proposal" would fail. > > >to fix a niche case and break the mainstream case from my window > > I understand it is important to keep the existing ecosystem workable (not > just mainstream cases), > however, I truly do not understand the failure mode you have in mind. > With your mode the end user writes in his pom "i want v1" and with your mechanism you do resolve v2 which doesn't have to be backward compat so there is no reason it works (and in practise it wouldn't with a lot of libs). > > Vladimir >
