Fixed spelling error in howto (#1381)

This commit is contained in:
Kyle Carter
2020-04-16 05:56:46 -06:00
committed by GitHub
parent b4ae35d602
commit d2ceaf6886

View File

@@ -461,7 +461,7 @@ To work with a Gradle project:
[source,groovy,indent=0]
----
ext {
conractsGroupId = "com.example"
contractsGroupId = "com.example"
contractsArtifactId = "common-repo"
contractsVersion = "1.2.3"
}
@@ -480,8 +480,8 @@ configurations {
[source,groovy,indent=0]
----
dependencies {
contracts "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
testCompile "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
contracts "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
testCompile "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
}
----
====
@@ -1455,4 +1455,4 @@ If you want the plugins not to fail the build when no contracts were found, you
If a contract is in progress, it means that the on the producer side tests will not be generated, but the stub will be. You can read more about this in <<project-features.adoc#contract-dsl-in-progress, this section>> of the documentation.
In a CI build, before going to production, you would like to ensure that no in progress contracts are there on the classpath. That's because you may lead to false positives. That's why, by default, in the Spring Cloud Contract plugin, we set the value of `failOnInProgress` to `true`. If you want to allow such contracts when tests are to be generated, just set the flag to `false`.
In a CI build, before going to production, you would like to ensure that no in progress contracts are there on the classpath. That's because you may lead to false positives. That's why, by default, in the Spring Cloud Contract plugin, we set the value of `failOnInProgress` to `true`. If you want to allow such contracts when tests are to be generated, just set the flag to `false`.