How to Exclude Specific Transitive Dependencies in Gradle: A Solution for Excluding slf4j-log4j12

Excluding Specific Dependencies During Gradle Build

Gradle allows excluding specific transitive dependencies to avoid unwanted artifacts in your built jar files. In this article, we'll explore how to exclude org.slf4j:slf4j-log4j12 using Gradle configurations.

Problem Statement

A Gradle project using the application plugin encountered challenges excluding slf4j-log4j12 from its runtime dependencies. Initial attempts to exclude it using the runtime.exclude configuration excluded all org.slf4j artifacts, including slf4j-api.

Solution

To resolve the issue, use the following syntax to specify both the group and module:

configurations {
  runtime.exclude group: "org.slf4j", module: "slf4j-log4j12"
}

This approach ensures the exclusion of only the desired dependency, leaving other org.slf4j artifacts unaffected.

Additional Notes

When excluding from an individual dependency, only the group and module properties are available as predicates. Unlike dependency declarations, you cannot specify arbitrary properties such as name.

The concept of a "module" in Gradle aligns with the Maven notion of artifactId. In the example above, slf4j-log4j12 represents the module. To determine the module name for a Maven artifact, refer to its artifactId component.

The above is the detailed content of How to Exclude Specific Transitive Dependencies in Gradle: A Solution for Excluding slf4j-log4j12. For more information, please follow other related articles on the PHP Chinese website!