Sorry I was not clear, what I was trying to say is: maven has logging built in, if you need a logfile you can pass the -l switch or re-configure slf4j. It also has some control over the loglevel (-X). Most users dont need it because they (think CI Server) just catch stdout.
http://maven.apache.org/maven-logging.html Gruss Bernd Am Mon, 5 May 2014 15:14:33 -0500 schrieb Paul Benedict <pbened...@apache.org>: > -X is debug/stack traces, right? That's great when you want a > slosh-load of debug information, but that's only useful when you're > looking for a problem. There's no recourse when problems oddball > conditions occur with -X not enabled. My point is Maven and Maven > plugins should be able to log those abnormal conditions in the course > of a normal build. We shouldn't have to dump the world -- especially > when the problem is not always repeatable. > > > > > Cheers, > Paul > > > On Mon, May 5, 2014 at 2:38 PM, Bernd Eckenfels > <e...@zusammenkunft.net>wrote: > > > Am Mon, 5 May 2014 14:17:50 -0500 > > schrieb Paul Benedict <pbened...@apache.org>: > > > > > What should be logged? Warnings. I actually would propose > > > exceptions too because them on the screen only help if you have > > > "logging" like a Hudson instance to view them. > > > > Uh, what is wrong with mvn -X -l? > > > > Gruss > > Bernd > > > > --------------------------------------------------------------------- > > 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
