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 location. There are situations that shouldn't kill a build (like
negative build times) but are extraordinary enough that they should be
dumped to a log file for studying. I think plugins should have the ability
to do such things for the sake of diagnosing out unfavorable
conditions/bugs in the code.

BTW, this is a different feature than debug info and stack traces. I don't
want to bug the user with more on their screen. I just want normal builds
to run like they do except introduce a warning log.

Thoughts?

Cheers,
Paul

Reply via email to