From bc1bdb7d1681fc2085966356d1f814643b2b1cbd Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Sat, 23 Apr 2016 23:26:51 +0200 Subject: [PATCH] Fixed docs --- docs/src/docs/asciidoc/stubrunner_msg.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/docs/asciidoc/stubrunner_msg.adoc b/docs/src/docs/asciidoc/stubrunner_msg.adoc index 7ce50d7b25..617ab903ee 100644 --- a/docs/src/docs/asciidoc/stubrunner_msg.adoc +++ b/docs/src/docs/asciidoc/stubrunner_msg.adoc @@ -45,7 +45,7 @@ To trigger a message it's enough to use the `StubTiggerer` interface: [source,groovy] ---- -include::../../stub-runner/src/main/groovy/io/codearte/accurest/stubrunner/StubTriggerer.groovy[] +include::../../../../stub-runner/stub-runner/src/main/groovy/io/codearte/accurest/stubrunner/StubTriggerer.groovy[] ---- For convenience the `StubFinder` interface extends `StubTrigger` so it's enough to use only one in your tests.