This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch maven2surefire-jvm-communication
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git.
discard c5757cc keeping backwards compatibility - printing corrupted stream
omit 8458c10 [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM.
Extensions API and SPI. Polymorphism for remote and local process communication.
add c799b3c added ASF Jira badge
add 3a6807c fixed broken links (MPIR 3)
add c3ef6d8 fixed broken links (MPIR 3)
add 31461e2 added GitHub configuration
add 5f2c5ba update commons compress
add b1f7a69 Merge pull request #282 from apache/pom
add ebbcdbf README improvement
new 6fb505c [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM.
Extensions API and SPI. Polymorphism for remote and local process communication.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (c5757cc)
\
N -- N -- N refs/heads/maven2surefire-jvm-communication (6fb505c)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.asf.yaml | 26 ++++++++++++++++++++++
README.md | 4 +++-
maven-surefire-plugin/src/site/apt/index.apt.vm | 8 +++----
.../src/site/apt/index.apt | 8 +++----
pom.xml | 2 +-
5 files changed, 38 insertions(+), 10 deletions(-)
create mode 100644 .asf.yaml
