Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.4.0</version>
<version>99.0-does-not-exist</version>
</dependency>
Comment on lines 298 to 302

@gitar-bot gitar-bot Bot Nov 12, 2026 •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Bug: 99.0-does-not-exist is an empty stub jar, not a commons-logging release

commons-logging:commons-logging:99.0-does-not-exist is not a real release. It is the empty placeholder jar from the linked "no more commons-logging" blog post. People use it to keep commons-logging off the classpath when they bridge to SLF4J. Renovate read the version string as a major upgrade. This entry is in the root <dependencyManagement>, so every commons-logging dependency in the reactor gets forced to the empty jar, transitive ones included. That covers the provided dependency in sonar-java-plugin/pom.xml, which is also on the test classpath. Any code or test that loads org.apache.commons.logging.LogFactory would then fail with NoClassDefFoundError. The repo has no jcl-over-slf4j bridge to provide those classes. This PR swaps a working 1.4.0 library for an artifact with no classes in it. Close the PR and keep 1.4.0. Add a Renovate rule so the bot stops proposing this pseudo-version.

Was this helpful? React with πŸ‘ / πŸ‘Ž

<dependency>
<groupId>org.apache.maven</groupId>
Expand Down
Loading