elharo commented on PR #2041: URL: https://github.com/apache/maven/pull/2041#issuecomment-2598299981
You're assuming they're being used by a Maven 4 plugin following the rules. That's certainly one way they will be used, but they will also be used by devs who add the Maven artifacts to their build file because their web app wants to stripLeadingAndTrailingQuotes from some string somewhere, and this looks like it does it. Developers can and do wire in utility methods that pull in frameworks the size of Spring because they want half-baked, buggy string processing utility. I've seen it before. I'm sure I'll see it again. But this is not just about developers who use the jars in ways that aren't planned for or intended. Reducing the public API footprint also makes it easier for tools like static analyzers and compilers to reason about the code. And most importantly, reducing the public API surface makes it easier for humans working on this code base to see what it does in one place. Separating tightly coupled pieces into separate files makes code much harder to read and understand. -- 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]
