ppkarwasz commented on issue #213: URL: https://github.com/apache/logging-log4j-transform/issues/213#issuecomment-3162622961
> I'm not 100% sure what you mean by "support." We could interpret keys that never actually existed like `customLevels`, but which users are very likely to have added by similarily to existing constructs. >The goal is to produce an output file with equivalent logging behavior to the input file. I think the reasonable behaviors here are "don't emit invalid configuration" and "_do_ emit a warning when known obsolete/meaningless keys are encountered and being ignored." I believe we already do emit warnings on unknown keys, but only for V1 configuration, where the list of properties is basically fixed. When converting from V2 configuration files, we don't really know all the properties especially for custom Log4j Core plugins. However in the particular case of `rootLogger` and `logger` the plugins are fixed, so I could add warnings for unknown properties. -- 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
