如何在子POM中排除父POM依赖？特定子模块需调整JUnit作用域

Let's break down your two key requirements clearly—adjusting JUnit's scope in a specific child module while preserving the parent's test scope, and excluding unwanted parent dependencies when needed.

1. Override JUnit's Scope in a Child Module #

Since your parent POM locks JUnit to test scope (which is standard for most modules), but you need it available in production code for one child module, the fix is straightforward: redeclare the JUnit dependency in the child POM with your desired scope. Maven lets child modules override parent dependency configurations by redefining the dependency entry.

Parent POM Reference (for context): #

<dependencies>
  <dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>4.13.2</version> <!-- Use your project's actual version -->
    <scope>test</scope>
  </dependency>
</dependencies>

Child Module POM Adjustment: #

<dependencies>
  <dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <!-- Version inherits from parent; no need to redefine unless you want a different one -->
    <scope>compile</scope> <!-- Use `runtime` if you only need it at runtime, not compilation -->
  </dependency>
</dependencies>

That's all! This child module will now use JUnit with compile scope, while every other child module keeps inheriting the parent's test scope as intended.

2. Excluding Parent Dependencies in a Child Module #

There are two common scenarios for excluding parent dependencies—let's cover both:

Scenario A: Exclude a direct parent dependency entirely #

If the parent POM includes a dependency you don't want in the child module at all, redeclare it in the child POM with provided scope. This tells Maven not to package the dependency with your child module, effectively excluding it:

<dependencies>
  <!-- Example: Excluding commons-lang3 inherited from parent -->
  <dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-lang3</artifactId>
    <scope>provided</scope>
  </dependency>
</dependencies>

Scenario B: Exclude a transitive dependency from a parent dependency #

If you want to keep the parent's main dependency but remove one of its transitive dependencies, use the <exclusions> tag to target the specific unwanted dependency:

<dependencies>
  <!-- Example: Keep parent's spring-core but exclude its commons-logging transitive dependency -->
  <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-core</artifactId>
    <exclusions>
      <exclusion>
        <groupId>commons-logging</groupId>
        <artifactId>commons-logging</artifactId>
      </exclusion>
    </exclusions>
  </dependency>
</dependencies>

Quick Pro Tip: #

Always run mvn dependency:tree in your child module to verify the final dependency tree—this helps you confirm your scope overrides and exclusions are working as expected.

内容的提问来源于stack exchange，提问作者PavlMits