elharo commented on issue #11582: URL: https://github.com/apache/maven/issues/11582#issuecomment-5531557715
This dramatically overstates the case and cherry picks evidence from a few random classes. This reversal of convention simply did not happen in Java 8. Maybe it started to pick up around Java 11, but I simply do not think it is reasonable to claim that this is the preferred or expected convention even in Java 26. Yes, both are used today but one has an explicit mandate and design going back 30 years and one doesn't. The mistake made here was to deprecate the existing methods that are already used and impose unnecessary costs on clients because of personal preference. Unfortunately that's a mistake that's been made again and again across Maven 4 APIs. This is hardly the only example. Lots of deprecation and API churn that makes the system more complex for no particular benefit. It prioritizes the preferences of some committers over the desire of the large installed base for compatible APIs that just work. Maven 4 hasn't shipped, so all this can still be fixed, but that does require refocusing on actual user facing features instead of random changes that deliver only negative user value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
