Re: [PR] Bump kotlin.version from 2.0.20 to 2.0.21 [logging-log4j-kotlin]

2024-10-11 Thread via GitHub 


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


-- 
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

Re: [PR] Provide guidelines and templates for the release process [logging-log4cxx]

2024-10-11 Thread via GitHub 


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


-- 
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

[I] `log4j-bom` leaks non-Log4j dependencies (logging-log4j2)

2024-10-11 Thread via GitHub 


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

   ## Description
   
   `log4j-bom` inherits from `logging-parent`. Unfortunately, this results in 
`log4j-bom` managing a number of dependencies that are unrelated to a 
consumer's use of Log4j2. Those dependencies are:
   
   - `biz.aQute.bnd:biz.aQute.bnd.annotation:7.0.0`
   - `com.github.spotbugs:spotbugs-annotations:4.8.6`
   - `org.jspecify:jspecify:1.0.0`
   - `org.osgi:osgi.annotation:8.1.0`
   - `org.osgi:org.osgi.annotation.bundle:2.0.0`
   - `org.osgi:org.osgi.annotation.versioning:1.1.2`
   
   `org.apache.maven.plugin-tools:maven-plugin-annotations:3.13.1` is also 
being managed but this is inherited from the `org.apache:apache` pom and has 
already been 
[reported](https://github.com/apache/maven-apache-parent/issues/265) and, 
pending an upgrade to use the new parent, 
[fixed](https://github.com/apache/maven-apache-parent/pull/266).
   
   This unwanted dependency management can conflict with a user's own 
dependency management for those dependencies. Depending on how that dependency 
management is configured, it may override it leaving a consumer using an 
unexpected version of a dependency.
   
   ## Configuration
   
   **Version:** 2.21.0 and later. The list of dependencies above is from 2.24.1.
   
   **Operating system:** Any
   
   **JDK:** Any
   
   ## Logs
   
   N/A
   
   ## Reproduction
   
   Run `mvn help:effective-pom` in a project with the following `pom.xml`:
   
   ```xml
   
   http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
com.example
log4j-bom-problem
0.0.1-SNAPSHOT



org.apache.logging.log4j
log4j-bom
2.24.1
import
pom



   
   ```
   
   The output will show a number of managed dependencies that aren't in the 
`org.apache.logging.log4j` group.
   
   
   


-- 
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

Re: [I] RollingFileAppender rotates files incorrectly on ext4 due to filesystem timestamp caching (logging-log4j2)

2024-10-11 Thread via GitHub 


kelunik commented on issue #3068:
URL: 
https://github.com/apache/logging-log4j2/issues/3068#issuecomment-2406993899

   @ppkarwasz Yes, I've of course looked at that ticket, but that didn't make 
it clear to me why modification time got changed to creation time.
   
   > your problem affects only the first rollover after the JVM starts. At this 
time Log4j Core uses the timestamp on the current log file to deduce when the 
last rollover must have occurred.
   
   Yes, I know, that's why I want to change the initial time back to the 
modification time instead of the creation time, but I don't want to cause a 
regression with that, that's why I want to understand the reasons for the 
original change there.


-- 
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

Re: [PR] Add automatic signing and uploading releases [logging-log4cxx]

2024-10-11 Thread via GitHub 


swebb2066 commented on PR #414:
URL: https://github.com/apache/logging-log4cxx/pull/414#issuecomment-2408303283

   The instruction in [the just added release 
instructions](https://github.com/apache/logging-log4cxx/blob/master/admin/releasing.md)
 can be simplified. Can you include the changes in this PR. Or should I do it 
and add it to the branch?
   
   I find it always useful to write instructions before writting the 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

Re: [PR] refactor(1.2-api): migrate to junit5 (logging-log4j2)

2024-10-11 Thread via GitHub 


github-actions[bot] commented on PR #3067:
URL: https://github.com/apache/logging-log4j2/pull/3067#issuecomment-2407207376

   
   
   
   
   Job
   Requested goals
   Build Tool Version
   Build Outcome
   Build Scan®
   
   
   build-macos-latest
   clean install
   3.9.8
   :x:
   https://ge.apache.org/s/rznnmfxg6aism"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   build-ubuntu-latest
   clean install
   3.9.8
   :x:
   https://ge.apache.org/s/trkctxmswvp64"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   build-windows-latest
   clean install
   3.9.8
   :x:
   https://ge.apache.org/s/qe47vvydfmugs"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   
   
   ## Generated by gradle/develocity-actions
   


-- 
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

[PR] Add automatic signing and uploading releases [logging-log4cxx]

2024-10-11 Thread via GitHub 


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

   This adds support for:
   
   - [ ] the verification of reproducibility of source archives.
   - [ ] signing of releases.
   - [ ] the generation of vote and announce e-mails.
   - [ ] the upload for releases to the staging Subversion repository
   


-- 
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

Re: [PR] Migrate `log4j-slf4j2-impl` to JUnit 5 (logging-log4j2)

2024-10-11 Thread via GitHub 


github-actions[bot] commented on PR #3080:
URL: https://github.com/apache/logging-log4j2/pull/3080#issuecomment-2407222157

   
   
   
   
   Job
   Requested goals
   Build Tool Version
   Build Outcome
   Build Scan®
   
   
   build-macos-latest
   clean install
   3.9.8
   :white_check_mark:
   https://ge.apache.org/s/aeqrmk2ketfj4"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   build-ubuntu-latest
   clean install
   3.9.8
   :white_check_mark:
   https://ge.apache.org/s/lma2mo46eckgw"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   build-windows-latest
   clean install
   3.9.8
   :white_check_mark:
   https://ge.apache.org/s/pqmilto6qp6na"; 
rel="nofollow">https://img.shields.io/badge/Build%20Scan%C2%AE-PUBLISHED-06A0CE?logo=Gradle";
 alt="Build Scan PUBLISHED" />
   
   
   
   
   ## Generated by gradle/develocity-actions
   


-- 
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

Re: [PR] Bump actions/upload-artifact from 4.4.2 to 4.4.3 [logging-parent]

2024-10-11 Thread via GitHub 


github-actions[bot] merged PR #267:
URL: https://github.com/apache/logging-parent/pull/267


-- 
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

Re: [PR] Add automatic signing and uploading releases [logging-log4cxx]

2024-10-11 Thread via GitHub 


ppkarwasz commented on PR #414:
URL: https://github.com/apache/logging-log4cxx/pull/414#issuecomment-2407887158

   There are some things left to fix:
   
   - I can not use `crazy-max/ghaction-import-gpg`, probably we need an INFRA 
ticket to install it on the repo. In the meantime I am using 
`actions/setup-java`, which is allowed to run.
   - The `generate-email.sh` script might need some massaging.
   - You might consider inlining the `generate-email.sh` script or run it in a 
different job, so the `sign-and-upload` does not require a Git checkout.


-- 
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

Re: [PR] Add automatic signing and uploading releases [logging-log4cxx]

2024-10-11 Thread via GitHub 


swebb2066 commented on code in PR #414:
URL: https://github.com/apache/logging-log4cxx/pull/414#discussion_r1797521246


##
.github/generate-email.sh:
##
@@ -0,0 +1,97 @@
+#!/bin/bash
+#
+# 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.
+#
+
+# Enable strict mode
+set -euo pipefail
+IFS=$'\n\t'
+
+stderr() {
+echo "$*" 1>&2
+}
+
+fail_for_invalid_args() {
+stderr "Invalid arguments!"
+stderr "Expected arguments:   "
+exit 1
+}
+
+# Check arguments
+[ $# -ne 3 ] && fail_for_invalid_args
+
+# Constants
+PROJECT_NAME="Apache Log4cxx"
+PROJECT_ID="log4cxx"
+PROJECT_VERSION="$2"
+PROJECT_SITE="https://logging.apache.org/$PROJECT_ID";
+PROJECT_STAGING_SITE="${PROJECT_SITE/apache.org/staged.apache.org}"
+PROJECT_REPO="https://github.com/apache/logging-log4cxx";
+COMMIT_ID="$3"
+PROJECT_DIST_URL="https://dist.apache.org/repos/dist/dev/logging/$PROJECT_ID/$PROJECT_VERSION";
+
+case $1 in
+
+vote)
+cat &2
+}
+
+fail_for_invalid_args() {
+stderr "Invalid arguments!"
+stderr "Expected arguments:   "
+exit 1
+}
+
+# Check arguments
+[ $# -ne 3 ] && fail_for_invalid_args
+
+# Constants
+PROJECT_NAME="Apache Log4cxx"
+PROJECT_ID="log4cxx"
+PROJECT_VERSION="$2"
+PROJECT_SITE="https://logging.apache.org/$PROJECT_ID";
+PROJECT_STAGING_SITE="${PROJECT_SITE/apache.org/staged.apache.org}"
+PROJECT_REPO="https://github.com/apache/logging-log4cxx";
+COMMIT_ID="$3"
+PROJECT_DIST_URL="https://dist.apache.org/repos/dist/dev/logging/$PROJECT_ID/$PROJECT_VERSION";
+
+case $1 in
+
+vote)
+cat