Hello Edvin. Yes, on unix it's more or less easy, windows don't have tee utility by default and I don't want asking my customers installing something like cygwin for this.
After all, i think it's not so bad idea for robust build tool having configurable logging, after all, what's the benefit of having few abstract logging classes in maven core over than just printing to System.err if it can't help configuring logging? What's the reason log4j logging used in maven 1.x was removed from m2 ? You wrote Tuesday, May 23, 2006, 10:24:40 AM: > if you're on *nix, and you want to ensure that you see any severe errors in > your logfile, you should also add '2>&1' to that command line. Usually, I'm > casually watching my builds, but want to have the option to go back and sift > through it, so I use this: mvn clean test 2>>&1 | tee output.log -- Best regards, zdv mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
