Treat check dependencies output as warnings

[mbektchiev]

Check dependencies has no output if no problems are found. Treat all unrecognized lines as warnings.

This way they won't be totally missing from the output generated by xcpretty. I'm not sure whether all of them are errors and would abort the build, that's why this is safer than treating them as errors. We can still add patterns for known errors, but it seems that they could come in various formats and it's not feasible to list them all.

[mbektchiev]

@supermarin, Can you review this one as well? And publishing a new version would be very nice to have, as there are some nice improvements since 0.2.5.

[supermarin]

@mbektchiev reviewed, although I'm not sure this is the right solution.

Check Dependencies is just a regular step (it's more like a section) that contains a few sub commands.
It should not be treated as a warning IMO.

Let me know your thoughts

[supermarin]

re: publishing a new version, will get on it today

[supermarin]

@mbektchiev published 0.2.6

[mbektchiev]

Yes, it indeed is a regular step and theoretically it could have output which shouldn't be treated as warnings. But unfortunately there are a lot of variations of messages that this step can generate and I haven't seen ones that are not in fact warnings or errors.

On the other hand, this step never prints anything if all checks are OK, that's why I think that this is still the better approach to the alternative of hiding the whole output.