Excluding Transitive Dependencies

To exclude a specific transitive dependency in Maven, you use the exclusions element inside the dependency declaration that's pulling in the unwanted library. You provide the groupId and artifactId of the transitive dependency you want to block, and Maven will skip downloading it when resolving that particular parent dependency. Here's a concrete example. Let's say you're adding Spring Framework five point three, which transitively depends on commons-logging. But your project uses SLF4J for all logging, and having commons-logging on the classpath creates conflicts because now you have two logging systems. In your pom.xml, inside the Spring dependency, you add an exclusions block. Inside that, you add an exclusion with the groupId commons-logging and artifactId commons-logging. Now when Maven downloads Spring, it skips commons-logging. But you're not done—you need to replace it with something. You add jcl-over-slf4j as a direct dependency, which is a bridge that redirects any commons-logging calls to SLF4J. Now everything uses one logging system. Another common scenario is security vulnerabilities. Your scanner flags Apache Commons Text one point nine as vulnerable, but it's coming in transitively from some legacy library. You exclude commons-text from that library's dependency declaration, then add Commons Text one point ten as a direct dependency in your pom. Now Maven uses the secure version. One mistake to avoid is excluding a library without understanding whether your code or other dependencies actually need it. If you exclude Jackson from a library and nothing else provides it, you'll get ClassNotFoundException at runtime. Always verify the exclusion is safe by running mvn dependency:tree afterward to see what's actually on your classpath.