Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin triggers deprecation warning with Gradle 8.11+ (when log4j dependency is present) #251

Open
jjohannes opened this issue Jan 17, 2025 · 0 comments
Assignees
Labels
a:bug Something isn't working

Comments

@jjohannes
Copy link

Expected Behavior

Plugin should not use deprecated Gradle API

Current Behavior

These deprecations can be observed:
https://scans.gradle.com/s/c72rjhbzovfoc/deprecations

It is apparently only triggered when Log4J is on the classpath.

at org.gradle.util.VersionNumber.logDeprecation(VersionNumber.java:38) 
at org.gradle.util.VersionNumber.parse(VersionNumber.java:175) 
at com.gradle.publish.PublishPlugin$Log4jVulnerabilityChecker.isVulnerableLog4jDependency(PublishPlugin.java:295)
at com.gradle.publish.PublishPlugin$Log4jVulnerabilityChecker.lambda$null$0(PublishPlugin.java:276)

Steps to Reproduce

  • Use Gradle 8.11.1 or higher to create a "Gradle Plugin Project"
  • Add id("com.gradle.plugin-publish") version "1.3.0" (this plugin) in build.gradle.kts
  • Add dependencies { implementation("org.apache.logging.log4j:log4j-core:2.24.1") } to build.gradle.kts
  • Run a build

Your Environment

https://scans.gradle.com/s/c72rjhbzovfoc#infrastructure

@jjohannes jjohannes added the a:bug Something isn't working label Jan 17, 2025
@ov7a ov7a self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants