Gradle转Maven后同一依赖类文件不一致问题求助

Hey there! Switching build tools can be tricky, especially when dependencies start behaving unexpectedly. Let's walk through the most likely reasons your Maven project is pulling a dependency with different class files than the Gradle version, and how to fix it.

Common Causes & Fixes #

1. Mismatched Dependency Coordinates or Hidden Classifiers #

Double-check that your Maven <dependency> block matches the Gradle declaration exactly, including any hidden classifiers you might have missed. For example:

• Gradle might have a classifier like this:

  compile 'org.springframework:spring-web:5.3.20:jdk11'
  

• If you forgot the <classifier> in Maven, it'll pull the default (JDK 8) jar instead:

  <!-- Wrong: missing classifier -->
  <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>5.3.20</version>
  </dependency>
  
  <!-- Correct: matches Gradle's classifier -->
  <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>5.3.20</version>
      <classifier>jdk11</classifier>
  </dependency>
  

Even a tiny difference here can result in completely different jar files with varying class implementations.

2. Divergent Dependency Resolution & Transitive Dependencies #

Gradle and Maven handle transitive dependencies and version conflicts slightly differently. To spot discrepancies:

• Run this in your Gradle project to get the full dependency tree:

  ./gradlew dependencies --configuration compileClasspath
  

• Run this in your Maven project to generate its tree:

  mvn dependency:tree
  

Compare the two trees for your problematic dependency. Look for:

• Version conflicts: Gradle might have picked a newer/older transitive dependency version than Maven.
• Excluded dependencies: Your Gradle build might have exclude rules that you haven't replicated in Maven. For example, if Gradle has:

  compile('org.springframework:spring-web:5.3.20') {
      exclude group: 'commons-logging', module: 'commons-logging'
  }
  

  You need to add the exclusion in Maven too:

  <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>5.3.20</version>
      <exclusions>
          <exclusion>
              <groupId>commons-logging</groupId>
              <artifactId>commons-logging</artifactId>
          </exclusion>
      </exclusions>
  </dependency>
  

3. Missing Repository Configurations #

Gradle might be pulling the dependency from a repository you haven't added to Maven. Check your Gradle build.gradle for repositories blocks:

repositories {
    mavenCentral()
    maven { url 'https://repo.spring.io/milestone' } // Example private/milestone repo
}

If there's a non-standard repo (like a company private repo, Spring Milestones, or Snapshots), you need to add it to your Maven pom.xml:

<repositories>
    <repository>
        <id>spring-milestones</id>
        <name>Spring Milestones</name>
        <url>https://repo.spring.io/milestone</url>
    </repository>
</repositories>

Without this, Maven might pull an older, incompatible version from Maven Central instead.

4. Local Cache Discrepancies #

Both Gradle and Maven cache dependencies locally, and sometimes these caches get out of sync or corrupted. Try:

• Delete the problematic dependency from Gradle's cache: ~/.gradle/caches/modules-2/files-2.1/<groupId>/<artifactId>
• Delete the same dependency from Maven's cache: ~/.m2/repository/<groupId>/<artifactId>
• Re-run both builds to pull fresh copies of the dependency.

5. Dependency Scope Mismatches #

While Gradle's old compile scope maps roughly to Maven's compile scope, double-check if you're using other scopes (like runtimeOnly in Gradle vs runtime in Maven). Using the wrong scope could lead to different class files being included in your build.

Next Steps #

If none of the above fixes work, try unpacking the Gradle-downloaded jar and the Maven-downloaded jar side by side. Compare the class files directly—this can reveal if one jar is missing classes, has different implementations, or is a different variant (e.g., a slimmed-down "runtime" jar vs a full "compile" jar).

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