Drop support for REST Assured

Closes gh-1000

Author: wilkinsona

config/checkstyle/checkstyle-suppressions.xml

@@ -3,6 +3,5 @@
 		"-//Checkstyle//DTD SuppressionFilter Configuration 1.2//EN"
 		"https://checkstyle.org/dtds/suppressions_1_2.dtd">
 <suppressions>
-	<suppress files="com[\\/]example[\\/]restassured" checks="IllegalImport" />
 	<suppress files="src[\\/]testFixtures" checks="JavadocPackage" />
 </suppressions>

docs/build.gradle

@@ -11,8 +11,9 @@ configurations {
 dependencies {
 	asciidoctorExt("io.spring.asciidoctor.backends:spring-asciidoctor-backends:0.0.5")
 
+	testCompileOnly("org.hamcrest:hamcrest-core")
+
 	testImplementation(project(":spring-restdocs-mockmvc"))
-	testImplementation(project(":spring-restdocs-restassured"))
 	testImplementation(project(":spring-restdocs-webtestclient"))
 	testImplementation("jakarta.servlet:jakarta.servlet-api")
 	testImplementation("jakarta.validation:jakarta.validation-api")

docs/src/docs/asciidoc/configuration.adoc

@@ -45,17 +45,6 @@ TIP: To configure a request's context path, use the `contextPath` method on `Moc
 
 
 
-[[configuration-uris-rest-assured]]
-==== REST Assured URI Customization
-
-REST Assured tests a service by making actual HTTP requests. As a result, URIs must be
-customized once the operation on the service has been performed but before it is
-documented. A
-<<customizing-requests-and-responses-preprocessors-modify-uris, REST-Assured-specific
-preprocessor>> is provided for this purpose.
-
-
-
 [[configuration-uris-webtestclient]]
 ==== WebTestClient URI Customization
 
@@ -90,12 +79,6 @@ include::{examples-dir}/com/example/mockmvc/CustomEncoding.java[tags=custom-enco
 include::{examples-dir}/com/example/webtestclient/CustomEncoding.java[tags=custom-encoding]
 ----
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/CustomEncoding.java[tags=custom-encoding]
-----
-
 TIP: When Spring REST Docs converts the content of a request or a response to a `String`, the `charset` specified in the `Content-Type` header is used if it is available.
 In its absence, the JVM's default `Charset` is used.
 You can configure the JVM's default `Charset` by using the `file.encoding` system property.
@@ -122,12 +105,6 @@ include::{examples-dir}/com/example/mockmvc/CustomFormat.java[tags=custom-format
 include::{examples-dir}/com/example/webtestclient/CustomFormat.java[tags=custom-format]
 ----
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/CustomFormat.java[tags=custom-format]
-----
-
 
 
 [[configuration-default-snippets]]
@@ -157,12 +134,6 @@ include::{examples-dir}/com/example/mockmvc/CustomDefaultSnippets.java[tags=cust
 include::{examples-dir}/com/example/webtestclient/CustomDefaultSnippets.java[tags=custom-default-snippets]
 ----
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/CustomDefaultSnippets.java[tags=custom-default-snippets]
-----
-
 
 
 [[configuration-default-preprocessors]]
@@ -187,12 +158,4 @@ include::{examples-dir}/com/example/webtestclient/CustomDefaultOperationPreproce
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/CustomDefaultOperationPreprocessors.java[tags=custom-default-operation-preprocessors]
-----
-<1> Apply a request preprocessor that removes the header named `Foo`.
-<2> Apply a response preprocessor that pretty prints its content.
-
 

docs/src/docs/asciidoc/customizing-requests-and-responses.adoc

@@ -24,14 +24,6 @@ include::{examples-dir}/com/example/webtestclient/PerTestPreprocessing.java[tags
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/PerTestPreprocessing.java[tags=preprocessing]
-----
-<1> Apply a request preprocessor that removes the header named `Foo`.
-<2> Apply a response preprocessor that pretty prints its content.
-
 Alternatively, you may want to apply the same preprocessors to every test.
 You can do so by using the `RestDocumentationConfigurer` API in your `@Before` method to configure the preprocessors.
 For example, to remove the `Foo` header from all requests and pretty print all responses, you could do one of the following (depending on your testing environment):
@@ -52,14 +44,6 @@ include::{examples-dir}/com/example/webtestclient/EveryTestPreprocessing.java[ta
 <1> Apply a request preprocessor that removes the header named `Foo`.
 <2> Apply a response preprocessor that pretty prints its content.
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/EveryTestPreprocessing.java[tags=setup]
-----
-<1> Apply a request preprocessor that removes the header named `Foo`.
-<2> Apply a response preprocessor that pretty prints its content.
-
 Then, in each test, you can perform any configuration specific to that test.
 The following examples show how to do so:
 
@@ -75,12 +59,6 @@ include::{examples-dir}/com/example/mockmvc/EveryTestPreprocessing.java[tags=use
 include::{examples-dir}/com/example/webtestclient/EveryTestPreprocessing.java[tags=use]
 ----
 
-[source,java,indent=0,role="secondary"]
-.REST Assured
-----
-include::{examples-dir}/com/example/restassured/EveryTestPreprocessing.java[tags=use]
-----
-
 Various built-in preprocessors, including those illustrated above, are available through the static methods on `Preprocessors`.
 See <<Preprocessors, below>> for further details.
 
@@ -129,7 +107,7 @@ Any occurrences that match a regular expression are replaced.
 TIP: If you use MockMvc or a WebTestClient that is not bound to a server, you should customize URIs by <<configuration-uris, changing the configuration>>.
 
 You can use `modifyUris` on `Preprocessors` to modify any URIs in a request or a response.
-When using REST Assured or WebTestClient bound to a server, this lets you customize the URIs that appear in the documentation while testing a local instance of the service.
+When using `WebTestClient` bound to a server, this lets you customize the URIs that appear in the documentation while testing a local instance of the service.