ppkarwasz commented on issue #3779: URL: https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3239441460
Hi all, As far as I can tell, this is a *cosmetic/false-positive* log line that appears **only** when using the older Spring Boot Dependency Management Gradle plugin; it does not affect resolution or runtime. Maven and Gradle’s native `platform()` aren’t impacted. Am I missing something? **On cutting a release.** Shipping a patch release solely to silence a log line is unusual and creates **upgrade churn** for many downstream projects (auto-generated Dependabot/Renovate PRs, internal approvals, release notes, and compatibility checks). We do hear you, though: if this message blocks Spring Boot or violates strict policies, we’ll try to accommodate. Our preference is to bundle it with other substantive fixes, but I believe there’s now enough to justify a `2.25.2` patch. * @snicoll If we publish a candidate next week, can the Spring Boot team validate it during the 72-hour vote window and give us a +1 before we announce? We can extend the vote if needed (as we did for `2.25.1`). In return for us prioritizing this fix in `2.25.2`, can we align on merging spring-projects/spring-boot#46410 so Spring Boot 4.x officially supports native builds with Log4j Core, assuming the candidate passes your CI? * @recaff Thanks for pushing to stay current, that’s our goal too. We try to bundle meaningful fixes so each Log4j Core release delivers real value rather than churn. **What would help.** The code change is trivial (duplicate a missing property in a child POM), but we need a minimal reproducer that **fails the build** when the offending log line appears. I spent a couple of hours updating apache/logging-log4j-samples#351; it works, but it relies on Gradle internals and isn’t clean. If you have a better approach, a small project or test we can run in CI would be ideal. Thanks for the patience and for pushing on build cleanliness, we share that goal. I’ll sync with the other maintainers and report back on the possibility of a `2.25.2` release. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
