This change also affects the case where you simply return a non-zero exit status, e.g. when `orm:schema-tool:drop` is called without `--force`:
![image](https://f.cloud.github.com/assets/821510/2499147/0cb2eaac-b352-11e3-9857-0e307ac9f840.png)

I've simply added
```php
throw new \RuntimeException('testing what happens when exceptions are thrown...');
```
to the `executeCommand()` function in the drop command, resulting in:
![image](https://f.cloud.github.com/assets/821510/2499219/ffac1d8c-b352-11e3-88b8-12321c7d0a39.png)

Note that the result without the patch is still `0`
![image](https://f.cloud.github.com/assets/821510/2499243/51d78b64-b353-11e3-8091-251f657f17de.png)

The RuntimeException use case can be fixed by using the Console exception strategy, but the first use case cannot.