[GitHub] [logging-log4j2] vy commented on a diff in pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

vy commented on code in PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#discussion_r1082265434


##
log4j-api/src/main/java/org/apache/logging/log4j/message/ReusableMessageFactory.java:
##
@@ -89,9 +83,21 @@ public static void release(final Message message) { // 
LOG4J2-1583
 }
 }
 
+@Override
+public void recycle(final Message message) {

Review Comment:
   How does this new method compare to `release(Message)`?



##
log4j-api/src/main/java/org/apache/logging/log4j/spi/RecyclerFactory.java:
##
@@ -0,0 +1,82 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache license, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the license for the specific language governing permissions and
+ * limitations under the license.
+ */
+package org.apache.logging.log4j.spi;
+
+import java.util.function.Consumer;
+import java.util.function.Supplier;
+
+/**
+ * Factory for {@link Recycler} strategies. Depending on workloads, different 
instance recycling strategies may be
+ * most performant. For example, traditional multithreaded workloads may 
benefit from using thread-local instance
+ * recycling while different models of concurrency or versions of the JVM may 
benefit from using an object pooling
+ * strategy instead.
+ *
+ * @since 3.0.0
+ */
+@FunctionalInterface
+public interface RecyclerFactory {
+
+/**
+ * Creates a new recycler using the given supplier function for initial 
instances. These instances have
+ * no cleaner function and are assumed to always be reusable.
+ *
+ * @param supplier function to provide new instances of a recyclable object
+ * @param  the recyclable type
+ * @return a new recycler for V-type instances
+ */
+default  Recycler create(final Supplier supplier) {
+return create(supplier, defaultCleaner());
+}
+
+/**
+ * Creates a new recycler using the given functions for providing fresh 
instances and for cleaning up
+ * existing instances for reuse. For example, a StringBuilder recycler 
would provide two functions:
+ * a supplier function for constructing a new StringBuilder with a 
preselected initial capacity and
+ * another function for trimming the StringBuilder to some preselected 
maximum capacity and setting
+ * its length back to 0 as if it were a fresh StringBuilder.
+ *
+ * @param supplier function to provide new instances of a recyclable object
+ * @param cleaner function to reset a recyclable object to a fresh state
+ * @param  the recyclable type
+ * @return a new recycler for V-type instances
+ */
+default  Recycler create(Supplier supplier, Consumer cleaner) {
+return create(supplier, cleaner, defaultCleaner());
+}
+
+/**
+ * Creates a new recycler using the given functions for providing fresh 
instances and for cleaning recycled
+ * instances lazily or eagerly. The lazy cleaner function is invoked on 
recycled instances before being
+ * returned by {@link Recycler#acquire()}. The eager cleaner function is 
invoked on recycled instances
+ * during {@link Recycler#release(Object)}.
+ *
+ * @param supplier function to provide new instances of a recyclable object
+ * @param lazyCleaner function to invoke to clean a recycled object before 
being acquired
+ * @param eagerCleaner function to invoke to clean a recycled object after 
being released
+ * @param  the recyclable type
+ * @return a new recycler for V-type instances
+ */
+ Recycler create(Supplier supplier, Consumer lazyCleaner, 
Consumer eagerCleaner);

Review Comment:
   What is the reason we need to introduce a lazy-cleaner? Why doesn't simply 
an eager one suffice?



##
log4j-api-test/src/test/java/org/apache/logging/log4j/spi/ThreadLocalRecyclerFactoryTest.java:
##
@@ -0,0 +1,51 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache license, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required 

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

ppkarwasz commented on PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#issuecomment-1398217767

   There is one `Recycler` usage case that is not covered by this PR: some 
objects like `LogBuilder` must be aware of the recycling lifecycle and be able 
to signal the recycler, when they are available.
   
   In the case of `LogBuilder` I imagine a sequence like this:
   
   - the logger acquires a `LogBuilder` from a `Recycler`,
   - the recycler calls `reset(Runnable release)` on the `LogBuilder`,
   - when the `log` method on the `LogBuilder` is called, the `LogBuilder` runs 
the `release` action.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] closed pull request #1089: Bump kafka-clients from 1.1.1 to 3.3.1

[GitBox]

dependabot[bot] closed pull request #1089: Bump kafka-clients from 1.1.1 to 
3.3.1
URL: https://github.com/apache/logging-log4j2/pull/1089


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1089: Bump kafka-clients from 1.1.1 to 3.3.1

[GitBox]

dependabot[bot] commented on PR #1089:
URL: https://github.com/apache/logging-log4j2/pull/1089#issuecomment-1398072392

   Superseded by #1217.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request, #1217: Bump kafka-clients from 1.1.1 to 3.3.2

[GitBox]

dependabot[bot] opened a new pull request, #1217:
URL: https://github.com/apache/logging-log4j2/pull/1217

   Bumps kafka-clients from 1.1.1 to 3.3.2.
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.kafka:kafka-clients&package-manager=maven&previous-version=1.1.1&new-version=3.3.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1397742320

   > Yes, I would expect the class that called `StackLocatorUtil` at the lowest 
index (or at least near the top), while the class that initiated execution on 
the thread (JUnit?) at the end.
   
   Java9 StackLocator uses "add" method which is for ArrayDeque equals to 
addLast, so it works as expected. Plus it has a unit test that verifies order 
of elements already 
(https://github.com/apache/logging-log4j2/blob/release-2.x/log4j-api-java9/src/test/java/org/apache/logging/log4j/util/java9/StackLocatorTest.java#L60).
 It also uses WALKER by default as 
"PrivateSecurityManagerStackTraceUtil.isEnabled()" always returns False. I 
assume it means we can skip additional tests for Java9 code


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

ppkarwasz commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1397550671

   Yes, I would expect the class that called `StackLocatorUtil` at the lowest 
index (or at least near the top), while the class that initiated execution on 
the thread (JUnit?) at the end.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1397333970

   > 
   
   Are you sure calling class should be the first? Screenshots from test 
project I attached before have calling class as the last element (index 26)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] timcoleman commented on issue #180: SetThreadDescription and GetThreadDescription are not properly linked on Windows

[GitBox]

timcoleman commented on issue #180:
URL: 
https://github.com/apache/logging-log4cxx/issues/180#issuecomment-1397141508

   This bit in threadutility.cpp causes an error:
   
   #if LOG4CXX_HAS_SETTHREADDESCRIPTION
#include 
#include 
   #endif
   
   Aside from that, it seems good.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] timcoleman commented on issue #180: SetThreadDescription and GetThreadDescription are not properly linked on Windows

[GitBox]

timcoleman commented on issue #180:
URL: 
https://github.com/apache/logging-log4cxx/issues/180#issuecomment-1397100265

   Hang on. I still think the code looks good, but I might have goofed 
something. Not enough coffee yet. 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] timcoleman commented on issue #180: SetThreadDescription and GetThreadDescription are not properly linked on Windows

[GitBox]

timcoleman commented on issue #180:
URL: 
https://github.com/apache/logging-log4cxx/issues/180#issuecomment-1397095671

   Yes, I built it and it is working for me. Logs are being written, and 
   the dependency walker doesn't show a missing dependency anymore.
   
   Thanks,
   
   Tim
   
   -- Original Message --
   From "Stephen Webb" ***@***.***>
   To "apache/logging-log4cxx" ***@***.***>
   Cc "timcoleman" ***@***.***>; "Author" 
   ***@***.***>
   Date 1/19/2023 2:02:19 AM
   Subject Re: [apache/logging-log4cxx] SetThreadDescription and 
   GetThreadDescription are not properly linked on Windows (Issue #180)
   
   >
   >Could you tell me if the windows_server_issue branch resolves this 
   >issue on your Windows server version please?
   >
   >—
   >Reply to this email directly, view it on GitHub 
   
>,
 
   >or unsubscribe 
   
>.
   >You are receiving this because you authored the thread.Message ID: 
   >***@***.***>
   >


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] swebb2066 commented on issue #180: SetThreadDescription and GetThreadDescription are not properly linked on Windows

[GitBox]

swebb2066 commented on issue #180:
URL: 
https://github.com/apache/logging-log4cxx/issues/180#issuecomment-1396526543

   Could you tell me if the windows_server_issue branch resolves this issue on 
your Windows server version please?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] swebb2066 opened a new pull request, #181: Allow use on Window Server 2016 (issue #180).

[GitBox]

swebb2066 opened a new pull request, #181:
URL: https://github.com/apache/logging-log4cxx/pull/181

   Put more than the first character of thread name into the event log on 
Windows.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

ppkarwasz commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1396467725

   @alex-dubrouski,
   
   Feel free to change `private` methods to package access. I think that we 
just need to test that `StackLocatorUtil#getCurrentStackTrace()` returns a 
`Deque` that has the calling class as first element.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1396276897

   I had quite hard time developing unit test for this class as it contains 
only static and private static methods. Final test verifies items in cache 
after executing "toExtendedStackTrace" method. Please provide your feedback and 
ideas.
   I will work on integration test for StackLocator


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] timcoleman opened a new issue, #180: SetThreadDescription and GetThreadDescription are not properly linked on Windows

[GitBox]

timcoleman opened a new issue, #180:
URL: https://github.com/apache/logging-log4cxx/issues/180

   In order to be used on Windows Server, the SetThreadDescription() and 
GetThreadDescription() functions need to be linked at run time, instead of at 
load time.
   
   The code as implemented works on Windows 10 (and I assume on Windows 11), 
but fails on Windows Server (I have tested 2016, but not any other Server 
versions).
   
   I have worked around this issue by disabling the symbol checks in 
CMakeLists.txt.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] rgoers commented on pull request #1215: Fix cron expression get a wrong previous fire time

[GitBox]

rgoers commented on PR #1215:
URL: https://github.com/apache/logging-log4j2/pull/1215#issuecomment-1387265885

   You can now create an issue in GitHub for this. We have a new changelog 
format so you can also add a changelog entry that references that issue.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz opened a new issue, #1216: Refresh CONTRIBUTING.md

[GitBox]

ppkarwasz opened a new issue, #1216:
URL: https://github.com/apache/logging-log4j2/issues/1216

   The 
[`CONTRIBUTING.md`](https://github.com/apache/logging-log4j2/blob/release-2.x/CONTRIBUTING.md)
 file needs some updates. E.g. the requirement for "minimal updates" needs to 
be more precise: Spotless might require reformatting entire files.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] vy opened a new issue, #19: FreeMarker integration is broken on Windows due to path issues

[GitBox]

vy opened a new issue, #19:
URL: https://github.com/apache/logging-log4j-tools/issues/19

   As [this failed CI 
run](/apache/logging-log4j2/actions/runs/3943007132/jobs/6747337526) indicates:
   ```
   java.lang.RuntimeException: failed exporting release from directory 
`D:\a\logging-log4j2\logging-log4j2\src\changelog\2.0-alpha1`
   at org.apache.logging.log4j.changelog.exporter.ChangelogExporter.main 
(ChangelogExporter.java:71)
   at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:279)
   at java.lang.Thread.run (Thread.java:750)
   Caused by: java.lang.RuntimeException: failed rendering template 
`D:\a\logging-log4j2\logging-log4j2\src\changelog\2.0-alpha1\.changelog.adoc.ftl`
 to file 
`D:\a\logging-log4j2\logging-log4j2\target\generated-sources\site\asciidoc\changelog\2.0-alpha1.adoc`
   at org.apache.logging.log4j.changelog.exporter.FreeMarkerUtils.render 
(FreeMarkerUtils.java:80)
   at 
org.apache.logging.log4j.changelog.exporter.ChangelogExporter.exportRelease 
(ChangelogExporter.java:170)
   at 
org.apache.logging.log4j.changelog.exporter.ChangelogExporter.exportRelease 
(ChangelogExporter.java:139)
   at org.apache.logging.log4j.changelog.exporter.ChangelogExporter.main 
(ChangelogExporter.java:63)
   at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:279)
   at java.lang.Thread.run (Thread.java:750)
   Caused by: freemarker.template.TemplateNotFoundException: Template not found 
for name 
"D:\\a\\logging-log4j2\\logging-log4j2\\src\\changelog\\2.0-alpha1\\.changelog.adoc.ftl".
   The name was interpreted by this TemplateLoader: 
FileTemplateLoader(baseDir="D:\", canonicalBasePath="D:\").
   Warning: The name contains backslash ("\") instead of slash ("/"); template 
names should use slash only.
   at freemarker.template.Configuration.getTemplate 
(Configuration.java:[28](https://github.com/apache/logging-log4j2/actions/runs/3943007132/jobs/6747337526#step:9:29)83)
   at freemarker.template.Configuration.getTemplate 
(Configuration.java:2685)
   at org.apache.logging.log4j.changelog.exporter.FreeMarkerUtils.render 
(FreeMarkerUtils.java:63)
   at 
org.apache.logging.log4j.changelog.exporter.ChangelogExporter.exportRelease 
(ChangelogExporter.java:170)
   at 
org.apache.logging.log4j.changelog.exporter.ChangelogExporter.exportRelease 
(ChangelogExporter.java:139)
   at org.apache.logging.log4j.changelog.exporter.ChangelogExporter.main 
(ChangelogExporter.java:63)
   at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:279)
   at java.lang.Thread.run (Thread.java:750)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] miracle-tree closed pull request #1215: Fix cron expression get a wrong previous fire time

[GitBox]

miracle-tree closed pull request #1215: Fix cron expression get a wrong 
previous fire time
URL: https://github.com/apache/logging-log4j2/pull/1215


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

ppkarwasz commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1386639067

   `StackLocator` is a complex feature with several different paths, so maybe 
I'll add a cheatsheet for the unity tests:
   
* the 
[`StackLocator#getCurrentStackTrace`](https://github.com/apache/logging-log4j2/blob/543bc664a88558f5a0bb523cbe7bbbc448e8d0e5/log4j-api-java9/src/main/java/org/apache/logging/log4j/util/StackLocator.java#L84)
 version in `log4j-api-java9` is used when running Java 9+. The tests are in 
the same module.
* the 
[`StackLocator#getCurrentStackTrace`](https://github.com/apache/logging-log4j2/blob/543bc664a88558f5a0bb523cbe7bbbc448e8d0e5/log4j-api/src/main/java/org/apache/logging/log4j/util/StackLocator.java#L197)
 version in `log4j-api` is used when running Java 8. It uses two 
implementations:
  * the _fast path_ provided by 
[`PrivateSecurityManagerStackTraceUtil`](https://github.com/apache/logging-log4j2/blob/543bc664a88558f5a0bb523cbe7bbbc448e8d0e5/log4j-api/src/main/java/org/apache/logging/log4j/util/PrivateSecurityManagerStackTraceUtil.java#L65)
 needs to be tested in the `log4j-api-test` module (in a "normal" `*Test` 
class),
  * the _slow path_ requires running the test with a security manager 
enabled. The test should be in the `log4j-api-test` module and be named `*IT`. 
The reason behind this is that "normal" tests in `log4j-api-test` run in 
parallel. Setting a security manager is a very disruptive operation, so we have 
a second test execution that runs `*IT` classes with a JVM-per-test 
configuration.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on a diff in pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

ppkarwasz commented on code in PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#discussion_r1073100498


##
log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThrowableProxyHelper.java:
##
@@ -85,7 +85,7 @@ static ExtendedStackTraceElement[] toExtendedStackTrace(
 stackLength = stackTrace.length;
 }
 final ExtendedStackTraceElement[] extStackTrace = new 
ExtendedStackTraceElement[stackLength];
-Class clazz = stack.isEmpty() ? null : stack.peek();
+Class clazz = stack.isEmpty() ? null : stack.peekLast();

Review Comment:
   Yes, I was referring to the broken slow path, which still uses `push` 
instead of `addLast`.
   
   Also:
   
   * `stack.isEmpty() ? null : stack.peekLast()` can be replaced with 
`stack.peekLast()`,
   * the comment in 
`org.apache.logging.log4j.util.PrivateSecurityManagerStackTraceUtil` states 
_"The size of the Deque is the number of methods on the execution stack. The 
first element is the class that started execution on this thread..."_ and is 
clearly not up-to-date.
   
   Testing the slow path is not easy: you need to create a test named `*IT` 
that has a security manager that does not allow the "createSecurityManager" 
permission. See `EnvironmentPropertySourceSecurityManagerIT` for inspiration.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] miracle-tree opened a new pull request, #1215: Fix cron expression get a wrong previous fire time

[GitBox]

miracle-tree opened a new pull request, #1215:
URL: https://github.com/apache/logging-log4j2/pull/1215

   For the method `CronExpression#getPrevFireTime`, currently only the minimum 
increment within a cycle is considered, and the cross-cycle situation is not 
involved, resulting in differences in the minimum increment obtained. The 
current commit is to fix this bug.
   
   I tried to create a Jira account to submit a bug, but so far no response has 
been received


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] swebb2066 merged pull request #178: Prevent compilation error in a MSYS2 environment using GCC

[GitBox]

swebb2066 merged PR #178:
URL: https://github.com/apache/logging-log4cxx/pull/178


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on a diff in pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on code in PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#discussion_r1072928929


##
log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThrowableProxyHelper.java:
##
@@ -85,7 +85,7 @@ static ExtendedStackTraceElement[] toExtendedStackTrace(
 stackLength = stackTrace.length;
 }
 final ExtendedStackTraceElement[] extStackTrace = new 
ExtendedStackTraceElement[stackLength];
-Class clazz = stack.isEmpty() ? null : stack.peek();
+Class clazz = stack.isEmpty() ? null : stack.peekLast();

Review Comment:
   Checked the code, I guess you mean that I need to update the slow path in 
"getCurrentStackTrace()" method which is normally not in use, please confirm.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on a diff in pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on code in PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#discussion_r1072928929


##
log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThrowableProxyHelper.java:
##
@@ -85,7 +85,7 @@ static ExtendedStackTraceElement[] toExtendedStackTrace(
 stackLength = stackTrace.length;
 }
 final ExtendedStackTraceElement[] extStackTrace = new 
ExtendedStackTraceElement[stackLength];
-Class clazz = stack.isEmpty() ? null : stack.peek();
+Class clazz = stack.isEmpty() ? null : stack.peekLast();

Review Comment:
   Checked the code, I guess you mean that I need to update the slow path in 
"getCurrentStackTrace()" method, please confirm.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski commented on a diff in pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski commented on code in PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#discussion_r1072914968


##
log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThrowableProxyHelper.java:
##
@@ -85,7 +85,7 @@ static ExtendedStackTraceElement[] toExtendedStackTrace(
 stackLength = stackTrace.length;
 }
 final ExtendedStackTraceElement[] extStackTrace = new 
ExtendedStackTraceElement[stackLength];
-Class clazz = stack.isEmpty() ? null : stack.peek();
+Class clazz = stack.isEmpty() ? null : stack.peekLast();

Review Comment:
   https://user-images.githubusercontent.com/36453467/213029221-bf8ab0c5-07f1-47d3-99c3-92c6326e635e.png";>
   https://user-images.githubusercontent.com/36453467/213029231-6d9dc2cf-dfe7-4cca-940d-3b48c5817437.png";>
   Order of elements in stack did not change between 2.17.1 and 2.19.0 at least 
from the index number point of view.
   I might have misunderstood you, sorry about that. Would like me to change 
the order of stack elements and preserve the current code in 
`ThrowableProxyHelper` or keep my changes to helper and don't change 
`StackLocator` as I assume these changed are mutually exclusive.
   I might need some time to develop a unit test as there is no tests for 
helper class so far
   
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on a diff in pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

ppkarwasz commented on code in PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#discussion_r1072880845


##
log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThrowableProxyHelper.java:
##
@@ -85,7 +85,7 @@ static ExtendedStackTraceElement[] toExtendedStackTrace(
 stackLength = stackTrace.length;
 }
 final ExtendedStackTraceElement[] extStackTrace = new 
ExtendedStackTraceElement[stackLength];
-Class clazz = stack.isEmpty() ? null : stack.peek();
+Class clazz = stack.isEmpty() ? null : stack.peekLast();

Review Comment:
   
[`Deque#peekLast()`](https://docs.oracle.com/javase/8/docs/api/java/util/Deque.html#peekLast--)
 already returns `null` if the deque is empty, so the check is not necessary.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] sudheerv commented on pull request #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

sudheerv commented on PR #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214#issuecomment-1385887173

   👍 Thanks @alex-dubrouski for finding the bug and providing the fix!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] alex-dubrouski opened a new pull request, #1214: This change fixes incorrect behavior of stack elements cache.

[GitBox]

alex-dubrouski opened a new pull request, #1214:
URL: https://github.com/apache/logging-log4j2/pull/1214

   Change of data structure from Stack to Deque (LIFO to FIFO) in this commit 
https://github.com/apache/logging-log4j2/commit/97f3153b73ab071a69c2e61e0130fd0104d45407
 broke cache logic. This bug causes a major performance regression. 
   ![Screen Shot 2023-01-11 at 6 31 58 
PM](https://user-images.githubusercontent.com/36453467/212984460-9c8a63c9-db7d-40c7-b17a-e5ec96a170ed.png)
   ![Screen Shot 2023-01-11 at 6 32 55 
PM](https://user-images.githubusercontent.com/36453467/212984479-1f308cfe-1d20-44ad-bf20-9aa5a75a9bc7.png)
   
   I created a small local project to reproduce the issue. I can attach it if 
needed.
   
   P.S. I signed ICLA and got a confirmation, but haven't got any response to 
my request to create a JIRA account, so can't create a bug.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] ppkarwasz closed issue #18: Og

[GitBox]

ppkarwasz closed issue #18: Og
URL: https://github.com/apache/logging-log4j-tools/issues/18


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz merged pull request #1205: Converter warning

[GitBox]

ppkarwasz merged PR #1205:
URL: https://github.com/apache/logging-log4j2/pull/1205


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed issue #1202: Pattern including PatternLayout Parameter disableAnsi=false emits a warning

[GitBox]

ppkarwasz closed issue #1202: Pattern including PatternLayout Parameter 
disableAnsi=false emits a warning
URL: https://github.com/apache/logging-log4j2/issues/1202


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] timcoleman opened a new issue, #179: Extra semicolons in include/log4cxx/pattern/patternconverter.h

[GitBox]

timcoleman opened a new issue, #179:
URL: https://github.com/apache/logging-log4cxx/issues/179

   When compiled with -Wpedantic, g++ complains of extra semicolons in 
include/log4cxx/pattern/patternconverter.h in this section:
   
   ```
DECLARE_LOG4CXX_PATTERN(PatternConverter);
BEGIN_LOG4CXX_CAST_MAP();
LOG4CXX_CAST_ENTRY(PatternConverter);
END_LOG4CXX_CAST_MAP();
   ```
   
   since the defines already include semicolons. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] jvz commented on a diff in pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

jvz commented on code in PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#discussion_r1071590544


##
log4j-core/src/main/java/org/apache/logging/log4j/core/layout/GelfLayout.java:
##
@@ -690,22 +726,17 @@ static CharSequence formatTimestamp(final long 
timeMillis) {
 if (timeMillis < 1000) {
 return "0";
 }
-final StringBuilder builder = getTimestampStringBuilder();
-builder.append(timeMillis);
-builder.insert(builder.length() - 3, '.');
+final StringBuilder builder = new StringBuilder(20);
+formatTimestampTo(builder, timeMillis);
 return builder;
 }
 
-private static final ThreadLocal timestampStringBuilder = 
new ThreadLocal<>();
-
-private static StringBuilder getTimestampStringBuilder() {

Review Comment:
   Also got a kick out of how pointless this buffer is when using the buffer 
provided by `AbstractStringLayout` already. The joys of new APIs!



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] jvz commented on a diff in pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

jvz commented on code in PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#discussion_r1071590262


##
log4j-core/src/main/java/org/apache/logging/log4j/core/layout/GelfLayout.java:
##
@@ -598,12 +636,22 @@ private StringBuilder toText(final LogEvent event, final 
StringBuilder builder,
 if (event.getThrown() != null || layout != null) {
 builder.append("\"full_message\":\"");
 if (layout != null) {
-final StringBuilder messageBuffer = getMessageStringBuilder();
-layout.serialize(event, messageBuffer);
-JsonUtils.quoteAsString(messageBuffer, builder);
+final StringBuilder messageBuffer = acquireStringBuilder();

Review Comment:
   Interesting little use case where you can now abuse the recursion support in 
`ThreadLocalRecyclerFactory` to get multiple recyclable objects. Already works 
as expected with the `QueueingRecyclerFactory` version.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] jvz commented on pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

jvz commented on PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#issuecomment-1384566193

   @vy care to have a look at my changes to the `Recycler` API?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] jvz commented on pull request #1194: Migrate Recycler API to log4j-api

[GitBox]

jvz commented on PR #1194:
URL: https://github.com/apache/logging-log4j2/pull/1194#issuecomment-1384562741

   Alright, I think I've figured out one key update to `RecyclerFactory` to 
make this API natural to use as a replacement for ad hoc 
`ThreadLocal`-style object reuse. This is to allow for two 
different types of cleaner functions to be supplied: one for cleaning a 
recycled instance when acquired, and another for cleaning a recycled instance 
when it's released. There are plenty of areas in Log4j where it's expected that 
`StringBuilder` instances will be trimmed right after being used, so this helps 
support that given that other areas that already use `Recycler` expect that the 
cleaner is lazily applied. Therefore, I've named them "eager" and "lazy" 
cleaner functions.
   
   I've also gone ahead and abstracted out some `Queue`-related utilities to 
more simply construct JCTools queue classes indirectly when available. Will 
have some commits to push shortly.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy merged pull request #1146: LOG4J2-3628 Replace maven-changes-plugin with a custom changelog implementation.

[GitBox]

vy merged PR #1146:
URL: https://github.com/apache/logging-log4j2/pull/1146


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] vy opened a new issue, #17: Unreleased directories are sorted incorrectly in `ChangelogExporter`

[GitBox]

vy opened a new issue, #17:
URL: https://github.com/apache/logging-log4j-tools/issues/17

   Read `.2.x.x` and `.3.x.x` directories are passed to the changelog template 
in `ChangelogExporter` in incorrect order, that is, `.2.x.x` first and then 
`.3.x.x`, whereas it should have been the other way round.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy closed issue #1207: Enforce signed commits

[GitBox]

vy closed issue #1207: Enforce signed commits
URL: https://github.com/apache/logging-log4j2/issues/1207


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy commented on issue #1207: Enforce signed commits

[GitBox]

vy commented on issue #1207:
URL: 
https://github.com/apache/logging-log4j2/issues/1207#issuecomment-1384476018

   Fixed in c6019c979ac07c1e664d066d01302561b47d2c72 and 
b61fd7b7fb5e9036b915992d5fa5522e72e424ae.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on issue #1207: Enforce signed commits

[GitBox]

ppkarwasz commented on issue #1207:
URL: 
https://github.com/apache/logging-log4j2/issues/1207#issuecomment-1384455056

   @vy,
   
   `spotless:check` is part of the build. We should document `spotless:apply` 
there so that contributors don't have to wonder why the build failed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy commented on issue #1207: Enforce signed commits

[GitBox]

vy commented on issue #1207:
URL: 
https://github.com/apache/logging-log4j2/issues/1207#issuecomment-1384447513

   > * running `spotless:apply`
   
   Is this really necessary given it is part of the build? It sounds like 
_"building the sources"_ or am I exaggerating?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy merged pull request #1172: Switch from JIRA to GitHub issues

[GitBox]

vy merged PR #1172:
URL: https://github.com/apache/logging-log4j2/pull/1172


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] closed pull request #1161: Bump maven-dependency-plugin from 3.3.0 to 3.4.0

[GitBox]

dependabot[bot] closed pull request #1161: Bump maven-dependency-plugin from 
3.3.0 to 3.4.0
URL: https://github.com/apache/logging-log4j2/pull/1161


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1161: Bump maven-dependency-plugin from 3.3.0 to 3.4.0

[GitBox]

dependabot[bot] commented on PR #1161:
URL: https://github.com/apache/logging-log4j2/pull/1161#issuecomment-1384430985

   Superseded by #1212.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1153: Bump spotless-maven-plugin from 2.27.2 to 2.28.0

[GitBox]

dependabot[bot] commented on PR #1153:
URL: https://github.com/apache/logging-log4j2/pull/1153#issuecomment-1384430982

   Superseded by #1213.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request, #1213: Bump spotless-maven-plugin from 2.27.2 to 2.30.0

[GitBox]

dependabot[bot] opened a new pull request, #1213:
URL: https://github.com/apache/logging-log4j2/pull/1213

   Bumps [spotless-maven-plugin](https://github.com/diffplug/spotless) from 
2.27.2 to 2.30.0.
   
   Changelog
   Sourced from https://github.com/diffplug/spotless/blob/main/CHANGES.md";>spotless-maven-plugin's
 changelog.
   
   [2.30.0] - 2022-09-14
   Added
   
   formatAnnotations() step to correct formatting of Java type 
annotations.  It puts type annotations on the same line as the type that they 
qualify.  Run it after a Java formatting step, such as 
googleJavaFormat(). (https://github-redirect.dependabot.com/diffplug/spotless/pull/1275";>#1275)
   
   Changes
   
   Bump default ktfmt version to latest 0.39 
-> 0.40 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1312";>#1312)
   Bump default ktlint version to latest 0.46.1 
-> 0.47.1 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1303";>#1303)
   
   Also restored support for older versions of ktlint back to 
0.31.0
   
   
   
   [2.29.0] - 2022-08-23
   Added
   
   scalafmt integration now has a configuration option 
majorScalaVersion that allows you to configure the Scala version 
that gets resolved from the maven artifact (https://github-redirect.dependabot.com/diffplug/spotless/pull/1283";>#1283)
   
   Converted scalafmt integration to use a compile-only source 
set (fixes https://github-redirect.dependabot.com/diffplug/spotless/issues/524";>#524)
   
   
   
   Changes
   
   Add the ktlint rule in error messages when 
ktlint fails to apply a fix (https://github-redirect.dependabot.com/diffplug/spotless/pull/1279";>#1279)
   Bump default scalafmt to latest 3.0.8 -> 
3.5.9 (removed support for pre-3.0.0) (https://github-redirect.dependabot.com/diffplug/spotless/pull/1283";>#1283)
   
   [2.28.1] - 2022-08-10
   Fixed
   
   Fix Clang not knowing the filename and changing the format (https://github-redirect.dependabot.com/diffplug/spotless/pull/1268";>#1268
 fixes https://github-redirect.dependabot.com/diffplug/spotless/issues/1267";>#1267).
   
   Changes
   
   Bump default diktat version to latest 1.2.1 
-> 1.2.3 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1266";>#1266)
   
   [2.28.0] - 2022-07-28
   Added
   
   Clang and Black no longer break the build when the binary is 
unavailable, if they will not be run during that build (https://github-redirect.dependabot.com/diffplug/spotless/pull/1257";>#1257).
   License header support for Kotlin files without package or 
@file but do at least have import (https://github-redirect.dependabot.com/diffplug/spotless/pull/1263";>#1263).
   
   [2.27.0] - 2022-06-30
   Added
   
   Support for MAC_CLASSIC (\r) line ending (https://github-redirect.dependabot.com/diffplug/spotless/pull/1243";>#1243
 fixes https://github-redirect.dependabot.com/diffplug/spotless/issues/1196";>#1196)
   
   Changes
   
   Bump default ktlint version to latest 0.45.2 
-> 0.46.1 (https://github-redirect.dependabot.com/diffplug/spotless/issues/1239";>#1239)
   
   Minimum supported version also bumped to 0.46.0 (we have 
abandoned strong backward compatibility for ktlint, from here on 
out Spotless will only support the most-recent breaking change).
   
   
   Bump default diktat version to latest 1.1.0 
-> 1.2.1 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1246";>#1246)
   
   Minimum supported version also bumped to 1.2.1 (diktat is 
based on ktlint and has the same backward compatibility issues).
   
   
   Bump default ktfmt version to latest 0.37 
-> 0.39 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1240";>#1240)
   
   [2.26.2] - 2022-06-11
   Fixed
   
   PalantirJavaFormatStep no longer needs the 
--add-exports calls in the org.gradle.jvmargs 
property in gradle.properties. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1233";>#1233)
   
   [2.26.1] - 2022-06-10
   Fixed
   
   (Second try) googleJavaFormat and 
removeUnusedImports works on JDK16+ without jvm args workaround. 
(https://github-redirect.dependabot.com/diffplug/spotless/pull/1228";>#1228)
   
   [2.26.0] - 2022-06-05
   Added
   
   Support for editorConfigOverride in ktlint. 
(https://github-redirect.dependabot.com/diffplug/spotless/pull/1218";>#1218
 fixes https://github-redirect.dependabot.com/diffplug/spotless/issues/1193";>#1193)
   
   Fixed
   
   google-java-format and RemoveUnusedImportsStep 
works on JDK16+ without jvm args workaround. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1224";>#1224
 fixes https://github-redirect.dependabot.com/diffplug/spotless/issues/834";>#834)
   
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/diffplug/spotless/commit/670c0ab54b97c0208df43dc5093c8c11c3e68aba";>670c0ab
 Update dependency org.eclipse.aether:aether-api to v0.9.1.v20140329
   https://github.com/diffplug/spotless/commit/27d3ae15dd85fe1a11edfe2950c3cb0c9c0b10f4";>27d3ae1
 Bump default ktfmt version

[GitHub] [logging-log4j2] dependabot[bot] closed pull request #1153: Bump spotless-maven-plugin from 2.27.2 to 2.28.0

[GitBox]

dependabot[bot] closed pull request #1153: Bump spotless-maven-plugin from 
2.27.2 to 2.28.0
URL: https://github.com/apache/logging-log4j2/pull/1153


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request, #1212: Bump maven-dependency-plugin from 3.3.0 to 3.5.0

[GitBox]

dependabot[bot] opened a new pull request, #1212:
URL: https://github.com/apache/logging-log4j2/pull/1212

   Bumps 
[maven-dependency-plugin](https://github.com/apache/maven-dependency-plugin) 
from 3.3.0 to 3.5.0.
   
   Commits
   
   https://github.com/apache/maven-dependency-plugin/commit/520f8fd6ba4a00a8a1174077d5610aa5ecae7595";>520f8fd
 [maven-release-plugin] prepare release maven-dependency-plugin-3.5.0
   https://github.com/apache/maven-dependency-plugin/commit/4b478d61e1e78f5bddda6d1256f91c357c2561a4";>4b478d6
 [MDEP-841] Explicitly start and end tables with Doxia Sinks in report 
renderers
   https://github.com/apache/maven-dependency-plugin/commit/799ff97da3130fe8dd1daf9e68405db066584080";>799ff97
 [MDEP-831] Remove dependency on commons-lang3 (https://github-redirect.dependabot.com/apache/maven-dependency-plugin/issues/270";>#270)
   https://github.com/apache/maven-dependency-plugin/commit/68b72723d3ece966078daec13567090b17280216";>68b7272
 [MDEP-837] Ignore reformat commit from git blame
   https://github.com/apache/maven-dependency-plugin/commit/cc082ea7d4af7db78c521d59360d261ffbc1b184";>cc082ea
 [MDEP-837] Reformat code after parent 38
   https://github.com/apache/maven-dependency-plugin/commit/803433bccf1bb4a562d05a6662189fde91184b6d";>803433b
 [MDEP-837] Upgrade Parent to 38
   https://github.com/apache/maven-dependency-plugin/commit/a05a2a4f5ce1e6d9053f6db9b84736e8bbc519b7";>a05a2a4
 Bump junit from 4.13 to 4.13.2 in /src/it/projects/tree-verbose-small
   https://github.com/apache/maven-dependency-plugin/commit/ea2a668dcb21e08c69d42c2cdbcf21483fdb3c01";>ea2a668
 remove unused beanutils dependency (https://github-redirect.dependabot.com/apache/maven-dependency-plugin/issues/268";>#268)
   https://github.com/apache/maven-dependency-plugin/commit/ea43fa6ae8b0504d12d794fdb6ff83e995f6a41a";>ea43fa6
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-dependency-plugin/commit/8fecf8a54af68c7b9cb97f90ac6b9c726e33e5ce";>8fecf8a
 [maven-release-plugin] prepare release maven-dependency-plugin-3.4.0
   Additional commits viewable in https://github.com/apache/maven-dependency-plugin/compare/maven-dependency-plugin-3.3.0...maven-dependency-plugin-3.5.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-dependency-plugin&package-manager=maven&previous-version=3.3.0&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] vy merged pull request #1166: Simplify site generation

[GitBox]

vy merged PR #1166:
URL: https://github.com/apache/logging-log4j2/pull/1166


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4cxx] rm5248 commented on issue #177: LOG4CXX_INSTANTIATE_EXPORTED_PTR issue on MSYS2 / GCC

[GitBox]

rm5248 commented on issue #177:
URL: 
https://github.com/apache/logging-log4cxx/issues/177#issuecomment-1384126363

   > Hence I guess the C++ standard really prohibits this type of template 
instantiations, and the issue could resurface later in e.g. future MSVC 
versions implementing the standard.
   
   MSVC has always been a weird compiler in my experience - as long as we check 
for `MSC_VER` we can also check for the compiler version / C++ standard and 
change the macro appropriately.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] StevenMassaro commented on pull request #1193: remove liquibase-log4j2 module

[GitBox]

StevenMassaro commented on PR #1193:
URL: https://github.com/apache/logging-log4j2/pull/1193#issuecomment-1384068628

   > Rebase/merge from current please? :)
   
   Done!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1210: fix: Restore previous behavior ignoring exceptions when translating a…

[GitBox]

ppkarwasz commented on PR #1210:
URL: https://github.com/apache/logging-log4j2/pull/1210#issuecomment-1384065955

   @wleese,
   
   Sorry, I forgot to comment on your issue report. Anyway, thank you for your 
issue report and PR. It is nice to see that someone **does** pay attention to 
Log4j2 warnings.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1128: [LOG4J2-3581] Provide a JCL to Log4j2 API binary weaver

[GitBox]

ppkarwasz commented on PR #1128:
URL: https://github.com/apache/logging-log4j2/pull/1128#issuecomment-1384004494

   Will be resubmitted to `logging-log4j-transform`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1128: [LOG4J2-3581] Provide a JCL to Log4j2 API binary weaver

[GitBox]

ppkarwasz closed pull request #1128: [LOG4J2-3581] Provide a JCL to Log4j2 API 
binary weaver
URL: https://github.com/apache/logging-log4j2/pull/1128


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] Deceptio opened a new issue, #1211: Hybrid example uses wrong class

[GitBox]

Deceptio opened a new issue, #1211:
URL: https://github.com/apache/logging-log4j2/issues/1211

   It seems that this example is not quite correct? 
   [Hybrid 
Example](https://logging.apache.org/log4j/2.x/manual/customconfig.html#Hybrid)
   
   There is no XMLConfiguration class but only an XmlConfiguration class. 
   Additionally the method createLogger is deprecated. 
   
   Maybe you should write a new example for the hybrid application.
   
   But maybe I understand the API wrong.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] wleese commented on pull request #1210: fix: Restore previous behavior ignoring exceptions when translating a…

[GitBox]

wleese commented on PR #1210:
URL: https://github.com/apache/logging-log4j2/pull/1210#issuecomment-1383873097

   I see a proper fix was provided in 
https://github.com/ppkarwasz/logging-log4j2/commit/5ddac7cd8a1e7ffe944f28086e1726d4818922bd


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] wleese closed pull request #1210: fix: Restore previous behavior ignoring exceptions when translating a…

[GitBox]

wleese closed pull request #1210: fix: Restore previous behavior ignoring 
exceptions when translating a…
URL: https://github.com/apache/logging-log4j2/pull/1210


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] wleese opened a new pull request, #1210: fix: Restore previous behavior ignoring exceptions when translating a…

[GitBox]

wleese opened a new pull request, #1210:
URL: https://github.com/apache/logging-log4j2/pull/1210

   … conversion parameter to an AnsiEscape enum


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1148: Bump junit-pioneer from 1.6.2 to 1.9.1

[GitBox]

ppkarwasz commented on PR #1148:
URL: https://github.com/apache/logging-log4j2/pull/1148#issuecomment-1383795952

   @dependabot rebase


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #503: Liquibase 4.x Compatibility

[GitBox]

ppkarwasz commented on PR #503:
URL: https://github.com/apache/logging-log4j2/pull/503#issuecomment-1383515373

   I close this, since Liquibase will publish their own plugin (cf. #1193).
   
   @nvoxland, thank You for your contribution.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #503: Liquibase 4.x Compatibility

[GitBox]

ppkarwasz closed pull request #503: Liquibase 4.x Compatibility
URL: https://github.com/apache/logging-log4j2/pull/503


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #601: LOG4J2-3193 Configuration precedence fix

[GitBox]

ppkarwasz closed pull request #601: LOG4J2-3193 Configuration precedence fix
URL: https://github.com/apache/logging-log4j2/pull/601


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #601: LOG4J2-3193 Configuration precedence fix

[GitBox]

ppkarwasz commented on PR #601:
URL: https://github.com/apache/logging-log4j2/pull/601#issuecomment-1383514234

   I am closing this since #742 refactored the property caching code and also 
fixed property priority.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] github-actions[bot] merged pull request #15: Bump freemarker from 2.3.31 to 2.3.32

[GitBox]

github-actions[bot] merged PR #15:
URL: https://github.com/apache/logging-log4j-tools/pull/15


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] github-actions[bot] merged pull request #16: Bump spotless-maven-plugin from 2.29.0 to 2.30.0

[GitBox]

github-actions[bot] merged PR #16:
URL: https://github.com/apache/logging-log4j-tools/pull/16


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j-tools] dependabot[bot] opened a new pull request, #16: Bump spotless-maven-plugin from 2.29.0 to 2.30.0

[GitBox]

dependabot[bot] opened a new pull request, #16:
URL: https://github.com/apache/logging-log4j-tools/pull/16

   Bumps [spotless-maven-plugin](https://github.com/diffplug/spotless) from 
2.29.0 to 2.30.0.
   
   Changelog
   Sourced from https://github.com/diffplug/spotless/blob/main/CHANGES.md";>spotless-maven-plugin's
 changelog.
   
   [2.30.0] - 2022-09-14
   Added
   
   formatAnnotations() step to correct formatting of Java type 
annotations.  It puts type annotations on the same line as the type that they 
qualify.  Run it after a Java formatting step, such as 
googleJavaFormat(). (https://github-redirect.dependabot.com/diffplug/spotless/pull/1275";>#1275)
   
   Changes
   
   Bump default ktfmt version to latest 0.39 
-> 0.40 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1312";>#1312)
   Bump default ktlint version to latest 0.46.1 
-> 0.47.1 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1303";>#1303)
   
   Also restored support for older versions of ktlint back to 
0.31.0
   
   
   
   
   
   
   Commits
   
   https://github.com/diffplug/spotless/commit/6cee33d6f035b462be5800c154d86ecad63cdd57";>6cee33d
 Published lib/2.30.0
   https://github.com/diffplug/spotless/commit/aadeaef0861309b8a4aadd5c04c8436451cdd82f";>aadeaef
 Bump KtLint default to 0.47.1 and restore support back to 0.31.0 (https://github-redirect.dependabot.com/diffplug/spotless/issues/1303";>#1303)
   https://github.com/diffplug/spotless/commit/dcdba4df7d739f503ba48e77525fd837787d53b4";>dcdba4d
 Update dependency org.eclipse.aether:aether-api to v0.9.1.v20140329
   https://github.com/diffplug/spotless/commit/b4d7019c09b9a0a34df79a5817f2e62a861a12e1";>b4d7019
 Merge branch 'main' into main-ktlint-versions
   https://github.com/diffplug/spotless/commit/670c0ab54b97c0208df43dc5093c8c11c3e68aba";>670c0ab
 Update dependency org.eclipse.aether:aether-api to v0.9.1.v20140329
   https://github.com/diffplug/spotless/commit/27d3ae15dd85fe1a11edfe2950c3cb0c9c0b10f4";>27d3ae1
 Bump default ktfmt version to v0.40 (https://github-redirect.dependabot.com/diffplug/spotless/issues/1312";>#1312)
   https://github.com/diffplug/spotless/commit/624af26e334821b6ab6d86423bff9a43a1d38aed";>624af26
 Update dependency org.mockito:mockito-core to v3.12.4 (https://github-redirect.dependabot.com/diffplug/spotless/issues/1315";>#1315)
   https://github.com/diffplug/spotless/commit/d80f076f1119153dc5865652eb6684fe101d5077";>d80f076
 Resolve changelog merge.
   https://github.com/diffplug/spotless/commit/864eb7a8fa2ec80728d7f8c6a6cc8ce6575c137e";>864eb7a
 Bump ktlint default version from 0.46.1 to 
0.47.1
   https://github.com/diffplug/spotless/commit/a3dc8f1337098bcc3b1834d9cb95bee05b2563e3";>a3dc8f1
 Merge branch 'renovate/ver_ktfmt' into main-ktlint-versions
   Additional commits viewable in https://github.com/diffplug/spotless/compare/lib/2.29.0...lib/2.30.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.diffplug.spotless:spotless-maven-plugin&package-manager=maven&previous-version=2.29.0&new-version=2.30.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To 

[GitHub] [logging-log4j-tools] dependabot[bot] opened a new pull request, #15: Bump freemarker from 2.3.31 to 2.3.32

[GitBox]

dependabot[bot] opened a new pull request, #15:
URL: https://github.com/apache/logging-log4j-tools/pull/15

   Bumps freemarker from 2.3.31 to 2.3.32.
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.freemarker:freemarker&package-manager=maven&previous-version=2.3.31&new-version=2.3.32)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz merged pull request #1209: Pre-2.20.0 dependency version dump

[GitBox]

ppkarwasz merged PR #1209:
URL: https://github.com/apache/logging-log4j2/pull/1209


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz commented on issue #1207: Enforce signed commits

[GitBox]

ppkarwasz commented on issue #1207:
URL: 
https://github.com/apache/logging-log4j2/issues/1207#issuecomment-1383269679

   - running `spotless:apply`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1185: Bump jetty-bom from 9.4.49.v20220914 to 9.4.50.v20221201

[GitBox]

dependabot[bot] commented on PR #1185:
URL: https://github.com/apache/logging-log4j2/pull/1185#issuecomment-1383265008

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1184: Bump netty-bom from 4.1.84.Final to 4.1.86.Final

[GitBox]

dependabot[bot] commented on PR #1184:
URL: https://github.com/apache/logging-log4j2/pull/1184#issuecomment-1383264927

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1180: Bump activemq-broker from 5.17.2 to 5.17.3

[GitBox]

dependabot[bot] commented on PR #1180:
URL: https://github.com/apache/logging-log4j2/pull/1180#issuecomment-1383264775

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1185: Bump jetty-bom from 9.4.49.v20220914 to 9.4.50.v20221201

[GitBox]

ppkarwasz closed pull request #1185: Bump jetty-bom from 9.4.49.v20220914 to 
9.4.50.v20221201
URL: https://github.com/apache/logging-log4j2/pull/1185


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1184: Bump netty-bom from 4.1.84.Final to 4.1.86.Final

[GitBox]

ppkarwasz closed pull request #1184: Bump netty-bom from 4.1.84.Final to 
4.1.86.Final
URL: https://github.com/apache/logging-log4j2/pull/1184


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1183: Bump jeromq from 0.5.2 to 0.5.3

[GitBox]

dependabot[bot] commented on PR #1183:
URL: https://github.com/apache/logging-log4j2/pull/1183#issuecomment-1383264838

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1183: Bump jeromq from 0.5.2 to 0.5.3

[GitBox]

ppkarwasz closed pull request #1183: Bump jeromq from 0.5.2 to 0.5.3
URL: https://github.com/apache/logging-log4j2/pull/1183


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1180: Bump activemq-broker from 5.17.2 to 5.17.3

[GitBox]

ppkarwasz closed pull request #1180: Bump activemq-broker from 5.17.2 to 5.17.3
URL: https://github.com/apache/logging-log4j2/pull/1180


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1179: Bump elasticsearch-rest-high-level-client from 7.17.6 to 7.17.8

[GitBox]

dependabot[bot] commented on PR #1179:
URL: https://github.com/apache/logging-log4j2/pull/1179#issuecomment-1383264640

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1179: Bump elasticsearch-rest-high-level-client from 7.17.6 to 7.17.8

[GitBox]

ppkarwasz closed pull request #1179: Bump elasticsearch-rest-high-level-client 
from 7.17.6 to 7.17.8
URL: https://github.com/apache/logging-log4j2/pull/1179


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1182: Bump groovy-bom from 3.0.13 to 3.0.14

[GitBox]

dependabot[bot] commented on PR #1182:
URL: https://github.com/apache/logging-log4j2/pull/1182#issuecomment-1383264553

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1182: Bump groovy-bom from 3.0.13 to 3.0.14

[GitBox]

ppkarwasz closed pull request #1182: Bump groovy-bom from 3.0.13 to 3.0.14
URL: https://github.com/apache/logging-log4j2/pull/1182


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1178: Bump spring-boot.version from 2.7.5 to 2.7.7

[GitBox]

ppkarwasz closed pull request #1178: Bump spring-boot.version from 2.7.5 to 
2.7.7
URL: https://github.com/apache/logging-log4j2/pull/1178


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1178: Bump spring-boot.version from 2.7.5 to 2.7.7

[GitBox]

dependabot[bot] commented on PR #1178:
URL: https://github.com/apache/logging-log4j2/pull/1178#issuecomment-1383264427

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1181: Bump spring-framework-bom from 5.3.23 to 5.3.24

[GitBox]

dependabot[bot] commented on PR #1181:
URL: https://github.com/apache/logging-log4j2/pull/1181#issuecomment-1383264339

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1181: Bump spring-framework-bom from 5.3.23 to 5.3.24

[GitBox]

ppkarwasz closed pull request #1181: Bump spring-framework-bom from 5.3.23 to 
5.3.24
URL: https://github.com/apache/logging-log4j2/pull/1181


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1177: Bump mockito.version from 4.8.1 to 4.11.0

[GitBox]

dependabot[bot] commented on PR #1177:
URL: https://github.com/apache/logging-log4j2/pull/1177#issuecomment-1383264258

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1177: Bump mockito.version from 4.8.1 to 4.11.0

[GitBox]

ppkarwasz closed pull request #1177: Bump mockito.version from 4.8.1 to 4.11.0
URL: https://github.com/apache/logging-log4j2/pull/1177


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1160: Bump jackson-bom from 2.13.4.20221013 to 2.14.1

[GitBox]

dependabot[bot] commented on PR #1160:
URL: https://github.com/apache/logging-log4j2/pull/1160#issuecomment-1383264139

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1160: Bump jackson-bom from 2.13.4.20221013 to 2.14.1

[GitBox]

ppkarwasz closed pull request #1160: Bump jackson-bom from 2.13.4.20221013 to 
2.14.1
URL: https://github.com/apache/logging-log4j2/pull/1160


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1158: Bump wiremock-jre8 from 2.34.0 to 2.35.0

[GitBox]

dependabot[bot] commented on PR #1158:
URL: https://github.com/apache/logging-log4j2/pull/1158#issuecomment-1383264035

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1158: Bump wiremock-jre8 from 2.34.0 to 2.35.0

[GitBox]

ppkarwasz closed pull request #1158: Bump wiremock-jre8 from 2.34.0 to 2.35.0
URL: https://github.com/apache/logging-log4j2/pull/1158


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1152: Bump spring-ws-core from 3.1.3 to 4.0.0

[GitBox]

dependabot[bot] commented on PR #1152:
URL: https://github.com/apache/logging-log4j2/pull/1152#issuecomment-1383263908

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. If you'd rather skip all updates until the next 
major or minor version, let me know by commenting `@dependabot ignore this 
major version` or `@dependabot ignore this minor version`. You can also ignore 
all major, minor, or patch releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1152: Bump spring-ws-core from 3.1.3 to 4.0.0

[GitBox]

ppkarwasz closed pull request #1152: Bump spring-ws-core from 3.1.3 to 4.0.0
URL: https://github.com/apache/logging-log4j2/pull/1152


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1151: Bump jmh.version from 1.35 to 1.36

[GitBox]

dependabot[bot] commented on PR #1151:
URL: https://github.com/apache/logging-log4j2/pull/1151#issuecomment-1383263829

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1151: Bump jmh.version from 1.35 to 1.36

[GitBox]

ppkarwasz closed pull request #1151: Bump jmh.version from 1.35 to 1.36
URL: https://github.com/apache/logging-log4j2/pull/1151


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] ppkarwasz closed pull request #1134: Bump cassandra.version from 3.11.13 to 3.11.14

[GitBox]

ppkarwasz closed pull request #1134: Bump cassandra.version from 3.11.13 to 
3.11.14
URL: https://github.com/apache/logging-log4j2/pull/1134


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1134: Bump cassandra.version from 3.11.13 to 3.11.14

[GitBox]

dependabot[bot] commented on PR #1134:
URL: https://github.com/apache/logging-log4j2/pull/1134#issuecomment-1383263737

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org