Eclipse运行时Gradle下载依赖报NoClassDefFoundError，本地Jar正常

This sounds like a classic Eclipse-Gradle synchronization issue, combined with potential classpath configuration quirks. Let's break down why this might be happening and how to fix it:

Possible Root Causes #

• Eclipse Classpath Desync: Even though the dependency shows up in Eclipse's "Project and External Dependencies" view, the underlying .classpath file (which controls what's actually loaded at runtime) might not have been properly updated for the Gradle-cached JAR. Eclipse often caches classpath entries, and manual changes or Gradle updates don't always trigger an immediate refresh.
• Permission Issues on Cached JARs: The Gradle cache directory (~/.gradle/caches/...) might have restrictive file permissions that prevent Eclipse from reading the JAR at runtime. Your local libs directory is part of your project, so it's likely configured with open read permissions by default.
• Legacy Dependency Scope: You're using the deprecated compile configuration. While it still works in older Gradle versions, the Eclipse Gradle plugin handles modern scopes like implementation more reliably, which could lead to subtle classpath inconsistencies.
• Eclipse Runtime Configuration Glitch: The run configuration for your project might not have picked up the Gradle-cached JAR, even though it's listed in the project dependencies. Sometimes run configurations retain old classpath entries until manually refreshed.

Step-by-Step Fixes #

1. Force a Full Gradle-Eclipse Sync
   This is the most common fix for desync issues. Run these commands from your project root:

   ./gradlew cleanEclipse eclipse
   

   Then in Eclipse:

   • Right-click your project → Refresh
   • Go to Project → Clean... and clean your project
     This will wipe old Eclipse configuration files and regenerate them directly from Gradle's model, ensuring the cached JAR path is properly added to the classpath.

2. Verify the .classpath File
   Open your project's .classpath file (in the root directory) and check for the commons-logging entry:

   • For the local JAR, you'll see something like:

     <classpathentry kind="lib" path="libs/commons-logging-1.2.jar"/>
     

   • For the Gradle-cached JAR, it should look like:

     <classpathentry kind="var" path="GRADLE_USER_HOME/caches/modules-2/files-2.1/commons-logging/commons-logging/1.2/[hash]/commons-logging-1.2.jar"/>
     

   If the cached JAR entry is missing, the cleanEclipse eclipse command above should add it.

3. Check Cached JAR Permissions
   Navigate to the cached JAR location in your file system:

   • On Windows: C:\Users\[YourUser]\.gradle\caches\modules-2\files-2.1\commons-logging\commons-logging\1.2\...
   • On macOS/Linux: ~/.gradle/caches/modules-2/files-2.1/commons-logging/commons-logging/1.2/...
     Right-click the JAR → Properties and ensure your user account has read permissions. On Linux/macOS, you can fix this with:

   chmod +r ~/.gradle/caches/modules-2/files-2.1/commons-logging/commons-logging/1.2/[hash]/commons-logging-1.2.jar
   

4. Update Dependency Scope
   Replace the deprecated compile configuration with implementation in your build.gradle:

   dependencies {
       // ... other dependencies
       implementation 'commons-logging:commons-logging:1.2'
   }
   

   Then re-run ./gradlew cleanEclipse eclipse and refresh Eclipse. Modern scopes are better supported by both Gradle and the Eclipse plugin, reducing synchronization issues.

5. Refresh Run Configuration
   If the issue persists only when running the project:

   • Right-click your project → Run As → Run Configurations
   • Select your run configuration → Go to the Classpath tab
   • Check if the Gradle-cached commons-logging JAR is listed under User Entries
   • If not, click Add External JARs... and select the cached JAR, or click Restore Defaults to regenerate the classpath from the project settings.

Summary #

In most cases, the problem boils down to Eclipse not properly syncing with Gradle's updated classpath. The cleanEclipse eclipse command combined with an Eclipse refresh/clean will resolve this. If that doesn't work, checking permissions or updating the dependency scope should fix the issue.

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