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
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
-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 ab
Am Mon, 5 May 2014 14:17:50 -0500
schrieb Paul Benedict :
> 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
In the instance of MNG-5256, the log file could dump the values that go
into calculating a negative build time. I think that would be very
insightful to trace the root cause.
What should be logged? Warnings. I actually would propose exceptions too
because them on the screen only help if you have "
Am 2014-05-05 16:20, schrieb Paul Benedict:
One thing that I like about Eclipse is that it contains a log file to
capture the unexpected warning or error. These warnings or errors may not
kill the program but at least I can peer inside to see what's going on.
With regard to MNG-5626, it makes me
One thing that I like about Eclipse is that it contains a log file to
capture the unexpected warning or error. These warnings or errors may not
kill the program but at least I can peer inside to see what's going on.
With regard to MNG-5626, it makes me wonder should Maven have a default
logging lo
