Repository navigation
Update dependency commons-logging:commons-logging to v99 - #6510
Conversation
|
Renovate Jira issue ID: SONARJAVA-7331 |
Code Review
|
| Auto-apply | Compact | Unblock |
|
|
|
Was this helpful? React with 👍 / 👎 | Gitar
| <dependency> | ||
| <groupId>commons-logging</groupId> | ||
| <artifactId>commons-logging</artifactId> | ||
| <version>1.4.0</version> | ||
| <version>99.0-does-not-exist</version> | ||
| </dependency> |
There was a problem hiding this comment.
⚠️ 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 👍 / 👎
|
vdiez
left a comment
There was a problem hiding this comment.
Auto-approved: Renovate dependency update.





This PR contains the following updates:
1.4.0→99.0-does-not-existConfiguration
📅 Schedule: (in timezone CET)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.