ppkarwasz commented on PR #192: URL: https://github.com/apache/ant/pull/192#issuecomment-1207894653
> We are maintaining things we accepted more than twentytwo years ago (`<netrexxc>` anyone :-) ) just to give a perspective on what maintenance involves. @bodewig, I perfectly understand the problem, since the Apache Logging project has the same problem with components nobody has been using for years. As Ralph said, it is to the Ant PMC to decide, if you are interested in this contribution. >Well, at least slf4j allows plugging several implementations, so if slf4j is ever added, then users could add whatever logging impl they want via the relevant slf4j-.. bridge. @vlsi, you perfectly know that the Log4j2 API has also several implementations (cf. [API separation](https://logging.apache.org/log4j/2.x/manual/api-separation.html)). >Well, I could easily imagine how users might want to make the logging level to be configurable. For instance, users might want to log private targets at a lower level than public ones, so the default output becomes more user-friendly. If such a need occurs I can modify the listener implementation to log a custom [`Message`](https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/message/Message.html) type that will wrap the `BuildEvent` object. This way the user will be able to write all sorts of filters. The `Message` interface provides a way to convert it to a list `(String, Object...)`, hence this listener could also be used with the Log4j2-to-SLF4J bridge. >Then, the contribution does not clarify the intended use case. Is it intended to be used by humans? If so, why the default Ant output is not enough? > >Is it supposed to be used for machine integration? (e.g. a CI server parsing log output) If so, why the default Ant's BuildListeners are not enough? I plan to use this listener at work to store the build logs in a structured way. -- 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: dev-unsubscr...@ant.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
