On 12.10.2012 00:01, Jason van Zyl wrote: > Ceki made some sample plugins and we'll post something tomorrow about > some options for integration. Basically Merged vs Mixed: do we want to > funnel everything into the the core logging backend, or let the plugin > completely decided by declaring both the API and implementation. The > outcome of this discussion will determine how to export (or not) > packages from the core.
I prefer to use the term "separated" logging to "mixed" logging. Now is a good time to discuss the "merged" vs. "separated" logging strategies for Maven. In the "merged" strategy, all logging goes through the slf4j-api instance created by maven-core, regardless of slf4j-related dependency declarations in a given plugin. In the "separated" strategy, a given plugin gets its own separate logging environment by declaring slf4j-related dependencies. The "separated" strategy raises the issue of whether getLog() and injected SLF4J loggers should be attached to the maven-core logging environment or the plugin's own logging environment. I am a big fan of "separated" logging strategy in application servers where forced merging the logs of all applications with the logs of the server is rather counter-intuitive not to say counter-productive. In the case of Maven however, I fail to see the added value in letting a given plugin have a separated logging environment. "Merged" logging offers the following advantages: 1) a very simple mental model for logging in Maven 2) seems that it is already implemented in trunk 3) few possible surprises in the future. and the following disadvantages: 1) the logging behavior of existing plugins (those declaring dependencies on slf4j) will change, i.e. merged into maven-core logging 2) relatively heavy handed approach In the context of Maven, is there any added value in pluging having a separated logging environment? If there is no added value, then merged logging is the way to go. -- Ceki 65% of statistics are made up on the spot --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
