ppkarwasz commented on issue #3794: URL: https://github.com/apache/logging-log4j2/issues/3794#issuecomment-3033389404
> I don't think it'd be too much to expect from those deviating from the defaults to know what they are doing. That’s fair in principle — but in practice, users often don’t fully understand how `classpath:` URLs are resolved. As an example, I wasn’t aware myself that under GraalVM, `classpath:` expands to a `resource:` URL. The behavior of `classpath:` can vary across environments — especially on different application servers — which can lead to subtle, hard-to-diagnose issues. This variability is exactly why it makes sense to handle `classpath:` as a special case. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
