Eclipse中POM文件Invalid END Header Error问题求助

Hey there, let's work through this Maven plugin issue you're hitting as a new Eclipse Java dev! That error about the "invalid END header" almost always means your local Maven repository has a corrupted copy of the maven-compiler-plugin 3.2 package—Maven can't read the plugin's lifecycle metadata because the downloaded JAR file is incomplete or messed up.

Here's a step-by-step fix that should get you back on track:

• Step 1: Locate the corrupted plugin folder
  Your local Maven repo is usually at ~/.m2/repository (Windows users will find it at C:\Users\<YourUsername>\.m2\repository). Navigate to this path inside the repo: org\apache\maven\plugins\maven-compiler-plugin\3.2
  This folder holds the broken plugin JAR and its associated checksum files.

• Step 2: Delete the entire 3.2 version folder
  Just delete the whole 3.2 folder—no need to pick through individual files. Maven will automatically re-download a fresh, uncorrupted copy later.

• Step 3: Refresh Maven dependencies in Eclipse
  Right-click your project in the Package Explorer → hover over Maven → select Update Project.... Check your project in the popup, then click OK. Eclipse will trigger Maven to pull the clean plugin files.

• If the error sticks? Force a full dependency refresh via command line
  Open Eclipse's built-in Terminal (or your system's command prompt), navigate to your project's root directory, and run this command:

  mvn clean install -U
  

  The -U flag forces Maven to update all dependencies and plugins, ensuring you get a complete, uncorrupted version of the compiler plugin.

Quick side note for new Maven users: Double-check your Eclipse Maven settings to make sure it's pointing to the right local repo. Go to Window → Preferences → Maven → User Settings, and confirm the Local Repository path matches the one you just cleaned up.

Pro tip: This "invalid END header" error is super common with Maven—it's almost never a problem with your POM file itself, just a messed-up download. Deleting the corrupted package and re-downloading is 99% of the fix!

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