This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a change to branch fix-win-terminal
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
omit a6cbd65e Add jline-native to the distribution
omit 5e93a078 Add the JLine diagnosis tool to the command line in the
native client
add 0e27c24a [1.x] mixup in case of DISPLAY messages type (#1037)
new f592c6b2 Add the JLine diagnosis tool to the command line in the
native client
new a5d5fd56 Add jline-native to the distribution
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 (a6cbd65e)
\
N -- N -- N refs/heads/fix-win-terminal (a5d5fd56)
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 2 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:
.../main/java-mvnd/org/mvndaemon/mvnd/client/DefaultClient.java | 2 +-
common/src/main/java/org/mvndaemon/mvnd/common/Message.java | 8 ++------
.../java/org/mvndaemon/mvnd/common/logging/TerminalOutput.java | 4 ++--
.../test/java/org/mvndaemon/mvnd/assertj/TestClientOutput.java | 2 +-
4 files changed, 6 insertions(+), 10 deletions(-)
