Skip to content

Commit 5ede508

Browse files
mpkorstanjempkorstanje
committed
[JUnit Platform] Fix dependency in README.md
Fixes: #2273
1 parent 264a5aa commit 5ede508

File tree

2 files changed

+44
-44
lines changed

2 files changed

+44
-44
lines changed

‎examples/calculator-java-junit4/pom.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
<version>6.10.3-SNAPSHOT</version>
88
</parent>
99

10-
<artifactId>calculator-java--junit4</artifactId>
10+
<artifactId>calculator-java-junit4</artifactId>
1111
<packaging>jar</packaging>
1212
<name>Examples: Calculator - Annotations - Junit4</name>
1313

‎junit-platform-engine/README.md‎

Lines changed: 43 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ Add the `cucumber-junit-platform-engine` dependency to your `pom.xml`:
77

88
```xml
99
<dependency>
10-
<groupId>io.cucumber</groupId>
11-
<artifactId>cucumber-junit-platform-engine</artifactId>
12-
<version>${cucumber.version}</version>
13-
<scope>test</scope>
10+
<groupId>io.cucumber</groupId>
11+
<artifactId>cucumber-junit-platform-engine</artifactId>
12+
<version>${cucumber.version}</version>
13+
<scope>test</scope>
1414
</dependency>
1515
```
1616

@@ -57,48 +57,48 @@ Add the following to your `pom.xml`:
5757

5858
```xml
5959
<dependencies>
60-
....
61-
<dependency>
62-
<groupId>org.junit.platform</groupId>
63-
<artifactId>junit-platform-launcher</artifactId>
64-
<version>${junit-platform.version}</version>
65-
<scope>test</scope>
66-
</dependency>
60+
....
61+
<dependency>
62+
<groupId>org.junit.platform</groupId>
63+
<artifactId>junit-platform-console</artifactId>
64+
<version>${junit-platform.version}</version>
65+
<scope>test</scope>
66+
</dependency>
6767
</dependencies>
6868

6969
<build>
70-
<plugins>
71-
<plugin>
72-
<groupId>org.apache.maven.plugins</groupId>
73-
<artifactId>maven-antrun-plugin</artifactId>
74-
<executions>
75-
<execution>
76-
<!--Work around. Surefire does not use JUnit's Test Engine discovery functionality -->
77-
<id>CLI-test</id>
78-
<phase>integration-test</phase>
79-
<goals>
80-
<goal>run</goal>
81-
</goals>
82-
<configuration>
83-
<target>
84-
<echo message="Running JUnit Platform CLI"/>
85-
<java classname="org.junit.platform.console.ConsoleLauncher"
86-
fork="true"
87-
failonerror="true"
88-
newenvironment="true"
89-
maxmemory="512m"
90-
classpathref="maven.test.classpath">
91-
<arg value="--include-engine"/>
92-
<arg value="cucumber"/>
93-
<arg value="--scan-classpath"/>
94-
<arg value="${project.build.testOutputDirectory}"/>
95-
</java>
96-
</target>
97-
</configuration>
98-
</execution>
99-
</executions>
100-
</plugin>
101-
</plugins>
70+
<plugins>
71+
<plugin>
72+
<groupId>org.apache.maven.plugins</groupId>
73+
<artifactId>maven-antrun-plugin</artifactId>
74+
<executions>
75+
<execution>
76+
<!--Work around. Surefire does not use JUnit's Test Engine discovery functionality -->
77+
<id>CLI-test</id>
78+
<phase>integration-test</phase>
79+
<goals>
80+
<goal>run</goal>
81+
</goals>
82+
<configuration>
83+
<target>
84+
<echo message="Running JUnit Platform CLI"/>
85+
<java classname="org.junit.platform.console.ConsoleLauncher"
86+
fork="true"
87+
failonerror="true"
88+
newenvironment="true"
89+
maxmemory="512m"
90+
classpathref="maven.test.classpath">
91+
<arg value="--include-engine"/>
92+
<arg value="cucumber"/>
93+
<arg value="--scan-classpath"/>
94+
<arg value="${project.build.testOutputDirectory}"/>
95+
</java>
96+
</target>
97+
</configuration>
98+
</execution>
99+
</executions>
100+
</plugin>
101+
</plugins>
102102
</build>
103103
```
104104
#### Use the Gradle JavaExec task ####

0 commit comments

Comments
 (0)