Remove hard setting of rspec formatter

[chrsgrrtt]

Overcomes deprecation issue: #41

[nilbus]

Thanks. I'll test it out sometime soon to confirm it works well for me. I'll merge this if so.

[paulgoetze]

@nilbus Any progress here? I would love to see this in a next release :)

[nilbus]

Hmm, I guess I forgot about this! 😵 Thanks for the reminder. I'll try to test it this weekend.

[nilbus]

@paulgoetze or @chrsgrrtt I'm having trouble reproducing this deprecation warning, and I believe it's because I'm using some different combination of gems than you. Could you please post a link to a gist containing your Gemfile.lock to help me get on the same relevant gem versions.

Also @paulgoetze, have you confirmed that everything works as you expect after removing the line removed in this pull request?

[paulgoetze]

Here‘s my Gemfile.lock: https://gist.github.com/paulgoetze/7277af0495c1aa69db15
I get the described deprecation warning with v0.2.2.

However, @chrsgrrtt, I cannot get the gem from your patch-1 branch running (v0.2.3.dev).
If I start up guard with bundle exec guard (which works fine with v0.2.2) it prints the watching message

INFO - Guard is now watching at /my/gem/path

and does nothing where it should run all specs.

If I try to run all specs by pressing RETURN it just fails and prints several error messages that it can‘t find e.g. my shared examples.