vendor directory support with additional feature

In some cases users run godog from inside a subpackage and vendor directory remains one level up.
This release has a patch to look for godog dependency package down until $GOPATH/src if project is in GOPATH.
See #35 for more details

vendor directory support

This release is a major step forward for godog, now we do not copy or rewrite any source files. Instead we use standard go tools:

• go test -c -work -o out.test to compile a tested package with test files included. Since it uses standard go command it supports all it's features. We can later maybe look how to add code coverage. It builds it even with CGO support.
• go tool compile - to compile our testmain entry point to run tests.
• go tool link - to create an executable godog suite file

1. We now fully support vendor directory and multiple GOPATH paths.
2. Fixed a bug with --stop-on-failure flag.
3. Added --no-colors flag, to strip ANSI color from output.
4. Now any context func needs to be exported. Same as go test requirement. It will show nice message on this issue.
5. Only go 1.5 and later versions from now on.

improved command flag management

v0.4.3

parse flags in runner command, to be able to show version or help, cl…

step def reference corrected in pretty print

v0.4.2

matched step func name and reference in pretty printer

regression was introduced with suite runner template

v0.4.1

fixes bug when there is more than one context registered, closes #32

refactored test suite build tooling

Merge pull request #29 from DATA-DOG/try-testmain

build test binary instead of single file to execute, use TestMain

JUnit formatter

• added JUnit compatible format to print xml results to stdout
• fixed #14
• made gherkin library compatibility support changes regarding scenario outline examples

explicit gherkin-go version

Gherkin-go had a backward incompatible change, from now on we will try to rely on gopkg.in for this dependency, see #17