在Eclipse IDE (Oxygen)提交者版本安装groovy-eclipse遇code=10053错误

Let's break down what's happening here and walk through how to resolve this error:

Why this error pops up #

First, that 0.0.0 version isn't a bug—it's a placeholder used in the build script for the alltests feature. This feature is a local, build-only component (it's never hosted on remote p2 repositories), so the error means either your local build didn't generate this feature, or your Eclipse p2 director command isn't looking in the right local repository for it.

Step-by-Step Fixes #

• First, complete a full local build of Groovy Eclipse
  The alltests feature gets generated as part of the full build process. From the root of your Groovy Eclipse repository, run this command to compile all modules, run tests, and generate the local p2 repository that includes the test feature:

  ./gradlew clean build p2Repository
  

  After the build finishes, the local p2 repository will be located in build/p2repository (or within the org.codehaus.groovy.eclipse.alltests/build/p2repository subdirectory).

• Update your p2 director command to include the local repository
  When running the director command from the documentation, you need to add your local p2 repository as a source. For example, if your repo is at /Users/your-username/groovy-eclipse/build/p2repository, modify the command to include:

  -repository file:///Users/your-username/groovy-eclipse/build/p2repository,http://download.eclipse.org/releases/oxygen
  

  Put the local repository path first—this tells p2 to check for local components before reaching out to remote repositories.

• Verify the local p2 repository has the alltests feature
  Navigate to your local p2 repo directory and check for a features/org.codehaus.groovy.alltests.feature_*.jar file (it'll have a real version number, not 0.0.0) with a corresponding feature.xml inside. If this file is missing, your build likely failed or skipped the test feature generation—check the build logs for errors related to the alltests module.

• Force a completely clean build
  Even after deleting ~/.gradle and ~/.p2, residual build caches can cause issues. Run this command to ensure a fresh start:

  ./gradlew clean build p2Repository --no-build-cache --no-daemon
  

  The --no-daemon flag ensures you're not using a leftover Gradle daemon that might hold cached old data.

Quick note on the 0.0.0 version #

That placeholder version is normal in the build script—when you run the full build, Gradle replaces it with the actual version of the Groovy Eclipse components you're building. The error shows 0.0.0 only because p2 can't find the locally built feature to resolve the real version.

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