> 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.
Could one possible case be a plugin which embeds some "framework" which uses slf4j to log to it's own log file(s)? And in this case you might want to keep the original framework's default logging behavior. Don't know of such case in reality, but it popped to my mind thinking about how the Cargo plugin works. It embeds an app server or web container and that container could be using slf4j already. Currently Cargo only supports Jetty in embedded mode though, and I don't know if Jetty uses slf4j or some other logging framework/API. If all logging from the embedded framework gets directed to the Maven output console, it could get messy. I'm thinking something like how the surefire plugin works where the user is directed to the surefire reports for further problem info (stacktraces etc.) Well, just some thoughts. /Anders > > > -- > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
