diff --git a/docs/userguide/002_Installation.adoc b/docs/userguide/002_Installation.adoc
index e7a1aca29a..f3b64b4acb 100644
--- a/docs/userguide/002_Installation.adoc
+++ b/docs/userguide/002_Installation.adoc
@@ -47,18 +47,6 @@ A typical Maven configuration could look like this:
maven-surefire-plugin
2.22.0
-
-
- org.junit.platform
- junit-platform-surefire-provider
- 1.3.1
-
-
- com.tngtech.archunit
- archunit-junit5-engine
- 0.10.0
-
-
@@ -71,16 +59,21 @@ A typical Maven configuration could look like this:
0.10.0
test
+
+ com.tngtech.archunit
+ archunit-junit5-engine
+ 0.10.0
+ test
+
...
----
-IMPORTANT: To run ArchUnit JUnit 5 tests within an IDE, it might unfortunately be necessary to add
- `archunit-junit5-engine` as a project dependency with scope `test` as well.
- Configuring `archunit-junit5-engine` as a dependency of the Surefire Plugin
- compensates Maven's lack of a test runtime scope, but is not reliably understood by IDEs.
+IMPORTANT: Unfortunately Maven lacks a test runtime scope, so the engine dependency must be added
+ to the test compile scope. Adding the engine dependency to the surefire-plugin
+ unfortunately does not work in the current version.
-The configuration for Gradle is much simpler due to the existence of a test runtime scope:
+The configuration for Gradle allows to clearly distinguish a test runtime scope:
[source,options="nowrap"]
.build.gradle
diff --git a/docs/userguide/html/000_Index.html b/docs/userguide/html/000_Index.html
index 86cb369cca..187f63291f 100644
--- a/docs/userguide/html/000_Index.html
+++ b/docs/userguide/html/000_Index.html
@@ -641,18 +641,6 @@
2.2. JUnit 5
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.22.0</version>
- <dependencies>
- <dependency>
- <groupId>org.junit.platform</groupId>
- <artifactId>junit-platform-surefire-provider</artifactId>
- <version>1.2.0</version>
- </dependency>
- <dependency>
- <groupId>com.tngtech.archunit</groupId>
- <artifactId>archunit-junit5-engine</artifactId>
- <version>0.10.0</version>
- </dependency>
- </dependencies>
</plugin>
</plugins>
</build>
@@ -665,6 +653,12 @@ 2.2. JUnit 5
<version>0.10.0</version>
<scope>test</scope>
</dependency>
+ <dependency>
+ <groupId>com.tngtech.archunit</groupId>
+ <artifactId>archunit-junit5-engine</artifactId>
+ <version>0.10.0</version>
+ <scope>test</scope>
+ </dependency>
</dependencies>
...
@@ -676,16 +670,15 @@ 2.2. JUnit 5
-To run ArchUnit JUnit 5 tests within an IDE, it might unfortunately be necessary to add
- archunit-junit5-engine as a project dependency with scope test as well.
- Configuring archunit-junit5-engine as a dependency of the Surefire Plugin
- compensates Maven’s lack of a test runtime scope, but is not reliably understood by IDEs.
+Unfortunately Maven lacks a test runtime scope, so the engine dependency must be added
+ to the test compile scope. Adding the engine dependency to the surefire-plugin
+ unfortunately does not work in the current version.
|
-
The configuration for Gradle is much simpler due to the existence of a test runtime scope:
+
The configuration for Gradle allows to clearly distinguish a test runtime scope: