>> 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.) > those would be the cases where the plugin would indicate that it wants > isolated logging.
Maybe I (as an end Maven user) don't want the plugin developer to decide this. It might be the decision for the build (or even the specific end user). Here's a use case: I very much dislike verbose output to the Maven console. Some people tend to add LOTS of debug logging in their unit tests, which makes it hard to read the console for me if I'm not the familiar with the build. For example, there could be exceptions, stack traces, etc. which are due to tests testing cases where there should be exceptions. So everything is good, but I see "ERROR", "FATAL", etc in the console and get worried. I rather do debugging if there's an reported error, but some developers rather find the problem through outputs. Should we decide in m-surefire-p if logging from JUnit tests should be in the console or not? I think not. It should be for the end user to decide (I guess that could be done in the Maven core logging config then) or for the specific build project (thus, checked into scm). Not sure how the latter should be handled though. Maybe I'm just making this too complicated. I think we need to keep this simple. And then refine it as we go. /Anders > > >> >> 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 >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
