This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch shellcheck10
in repository https://gitbox.apache.org/repos/asf/maven-wrapper.git
discard ac6c30c Bump shellcheck to 0.10.0
add 1830d81 [MWRAPPER-154] Bump commons-io:commons-io from 2.16.1 to
2.18.0 (#161)
add b2ff9cd [MWRAPPER-150] - Fails to validate checksums on MacOS Sequoia
(#155)
add 430fd0c [MWRAPPER-147] mvnw.cmd fails to launch maven if username
contains space
add 7af7d15 [MWRAPPER-146] Bad substitution on Windows if MVNW_REPOURL is
set on script-only (#151)
new bcdfe3e Bump shellcheck to 0.10.0
new 668089e Fix warning
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 (ac6c30c)
\
N -- N -- N refs/heads/shellcheck10 (668089e)
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:
maven-wrapper-distribution/src/resources/mvnw | 10 +++++-----
maven-wrapper-distribution/src/resources/only-mvnw | 2 +-
maven-wrapper-distribution/src/resources/only-mvnw.cmd | 6 +++---
maven-wrapper-plugin/pom.xml | 2 +-
pom.xml | 2 ++
5 files changed, 12 insertions(+), 10 deletions(-)
mode change 100644 => 100755 maven-wrapper-distribution/src/resources/mvnw
