On Mon, Jul 28, 2008 at 6:09 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: >>> == Colors for errors >> I like your use of color. Could you give me an example of a blue message? > > Right now we use warnings in three places. Deprecated warnings, for > every deprecated method or feature. In a few places, where we're not > sure it's an error but worth paying attention. For example, if you > run buildr package in a directory not associated with any project, it > warns you that "No projects defined for directory ...", but it still > runs that task -- it might do some other interesting things.
OK. I've never seen them because I never ran into these cases, but I agree they warrant a warning message. > The third place, a warning lists all the failed test cases for a > project. Typically, you'll also get an error message, unless you're > running with test=all, in which case it will keep running test cases > for other projects, so you can pick up these warnings from the > console. Although, maybe these should show as errors instead of > warnings? I consider a failing test as an error, but since I'm test-infected, I admit I'm biased. :-) >> Or maybe the last one should be merged with the 'fail' method. > > I think there's a reason to have both error and fail. Specifically, > the test=all option allows you to run all the test cases, ignoring > errors, so there's no failure, but you'll still want to see these > error messages. You're right. Lacton
