elharo commented on PR #849: URL: https://github.com/apache/maven-shade-plugin/pull/849#issuecomment-5540230690
I'll reopen and reconsider but so far I've seen demand from exactly *1* person. That's not sufficient. If you have references to the changes this imposes on downstream, please provide them. For now a plugin-specific logger level sounds like a reasonable workaround though I will note that depending on log messages for **anything** is a recipe for breakage and pain. That's not just in this plugin. That's not just in Maven. That's not just in Java. It's a really brittle antipattern. Log messages are not API and shouldn't be used as such. If you're doing that, you're going to have a bad day. -- 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]
