jvz commented on PR #2887: URL: https://github.com/apache/logging-log4j2/pull/2887#issuecomment-2310669473
While I like the `ServiceLoader` approach best (and don't think it's _that_ hard to back port; the main challenges there revolve around updating the annotation processor to generate the service classes as the `main` version has diverged considerably from `2.x`. However, that only solves the problem for plugins compiled against the version of Log4j that introduces support for it, and 3.0 seemed like a solid point for that. I agree with Volkan here that having three formats is not ideal, and even two formats is annoying enough (I had hoped to eliminate support for the .dat format in 3.0, but that's the only thing that allows for 2.x plugins to still be loadable due to annotation changes). Could we have some sort of compromise where the .dat parser can work in a lax mode or something where it tries to continue parsing a concatenated .dat file? -- 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]
