From ee5a1b997ec6101d313b94e233e65d9e6f7d1489 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Tue, 12 Sep 2017 11:40:56 +0200 Subject: [PATCH] Added a note about Rest Assured 3.0 --- docs/src/main/asciidoc/migrations.adoc | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/migrations.adoc b/docs/src/main/asciidoc/migrations.adoc index d306e206c1..5cd5952f32 100644 --- a/docs/src/main/asciidoc/migrations.adoc +++ b/docs/src/main/asciidoc/migrations.adoc @@ -154,6 +154,21 @@ In order to add support for `fromRequest.path`, the following methods had to be See https://github.com/spring-cloud/spring-cloud-contract/issues/388[issue 388] for more detail. -======= -// TODO 1.1.x -> 1.2.x +==== RestAssured 3.0 + +Rest Assured, used in the generated test classes, got bumped to `3.0`. If +you manually set versions of Spring Cloud Contract and the release train +you might see the following exception: + +[source,bash] +---- +Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (default-testCompile) on project some-project: Compilation failure: Compilation failure: +[ERROR] /some/path/SomeClass.java:[4,39] package com.jayway.restassured.response does not exist +---- + +This exception will occur due to the fact that the tests got generated with +an old version of plugin and at test execution time you have an incompatible +version of the release train (and vice versa). + +Done via https://github.com/spring-cloud/spring-cloud-contract/issues/267[issue 267] \ No newline at end of file