This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git
The following commit(s) were added to refs/heads/master by this push:
new d6db7c9 corrections in APT VM file which was not deployed to the
Apache site
d6db7c9 is described below
commit d6db7c9315a2a750b3433cda3f1e649448773aa6
Author: tibordigana <tibor.dig...@gmail.com>
AuthorDate: Sat Oct 31 00:44:39 2020 +0100
corrections in APT VM file which was not deployed to the Apache site
---
.../src/site/apt/examples/process-communication.apt.vm | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
a/maven-surefire-plugin/src/site/apt/examples/process-communication.apt.vm
b/maven-surefire-plugin/src/site/apt/examples/process-communication.apt.vm
index 75e553e..eaba32c 100644
--- a/maven-surefire-plugin/src/site/apt/examples/process-communication.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/process-communication.apt.vm
@@ -1,10 +1,10 @@
-------
-Using JUnit 5 Platform
-------
-Communication Channels in Surefire <us...@maven.apache.org>
-------
-2020-03-15
-------
+ ------
+ Using JUnit 5 Platform
+ ------
+ Communication Channels in Surefire <us...@maven.apache.org>
+ ------
+ 2020-03-15
+ ------
~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements. See the NOTICE file
@@ -32,11 +32,11 @@ Communication Channels used between the Maven Process and
Surefire Process
The communication channel can be changed even by the user in the user's POM.
The physical layer of the channel can be switched from Process Pipes to
TCP/IP.
The user select the default implementations in the POM or the user can
implement his own channel without asking
- the Apache Maven development team for a new support. This chapter will show
you how this can be accomplished.
+ the Apache Maven development team for providing a new support. Let's show
you how this can be accomplished.
* forkNode
- The configuration is done by using only one configuration parameter
<<<forkMode>>>.
+ The configuration is done by using only one configuration parameter
<<<forkNode>>>.
* The TCP/IP communication channel
