This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch update-license-files
in repository https://gitbox.apache.org/repos/asf/storm.git
discard 3524ea9b7 Regenerate license files after dependency changes
omit b04ba6749 build(deps): bump zookeeper.version from 3.9.5 to 3.9.6 in
/examples (#9120)
omit e707db037 build(deps): bump
io.github.git-commit-id:git-commit-id-maven-plugin (#9119)
omit 577f5c545 build(deps): bump
org.apache.maven.plugins:maven-surefire-report-plugin (#9117)
omit a093402dc build(deps): bump org.codehaus.mojo:exec-maven-plugin (#9116)
omit 97b9a6f8e build(deps): bump
com.fasterxml.jackson.core:jackson-databind (#9115)
omit d3252fc64 build(deps-dev): bump org.codehaus.mojo:taglist-maven-plugin
(#9114)
omit 5c9011e45 build(deps): bump activemq.version from 6.3.1 to 6.3.2
(#9113)
omit e8dc31c32 build(deps): bump
org.apache.maven.plugins:maven-compiler-plugin (#9112)
new 82e4cf7e3 Regenerate license files after dependency changes
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 (3524ea9b7)
\
N -- N -- N refs/heads/update-license-files (82e4cf7e3)
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:
DEPENDENCY-LICENSES | 3 +--
pom.xml | 14 +++++++-------
2 files changed, 8 insertions(+), 9 deletions(-)
