This is an automated email from the ASF dual-hosted git repository.
rgupta pushed a change to branch rg/136-logger-property-package-change
in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git
omit 5e4b128 Logger extension: update docs
omit 4d896b3 Move logger property to `extension` package
add e89fa1e Bump org.codehaus.mojo:build-helper-maven-plugin from 3.6.0
to 3.6.1 (#121)
add bcbcd91 Bump org.apache.maven.plugins:maven-shade-plugin from 3.6.0
to 3.6.1 (#134)
add 4564dff Bump junit.version from 5.12.0 to 6.0.1 (#141)
add 037ce89 Update `org.codehaus.mojo:exec-maven-plugin` to version
`3.5.0` (#99) (#99)
new 65985ad Move logger property to `extension` package
new 8e53c1c Logger extension: update docs
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 (5e4b128)
\
N -- N -- N refs/heads/rg/136-logger-property-package-change
(8e53c1c)
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:
pom.xml | 8 ++++----
.../.1.x.x/update_org_codehaus_mojo_exec_maven_plugin.xml | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
