在OS X上配置TEAMMATES项目时，运行gradlew setupEclipse报错求助

Hey there, let's break down the issues you're facing with setting up the TEAMMATES project in Eclipse on OS X El Capitan, and walk through actionable fixes to get your environment configured properly.

Common Causes for ./gradlew setupEclipse Failures #

Based on your setup (OS X El Capitan + Eclipse Oxygen Java EE), these are the most likely culprits:

• Java Version Mismatch: TEAMMATES typically requires Java 8 (the version best supported by Eclipse Oxygen), but El Capitan's pre-installed Java might be outdated or not aligned with the project's requirements.
• Gradle Wrapper Permissions/Execution Issues: El Capitan's strict system permissions can block the Gradle wrapper from running, or you might be using an incorrect execution syntax.
• Project Location Conflicts: If you cloned the repo to a system-protected folder (like /Applications or /Library), Gradle might lack write access to generate Eclipse config files.
• Eclipse Plugin Caching: Even after installing required plugins, Eclipse Oxygen's cached plugin data can cause conflicts during project setup.

Step-by-Step Fixes to Complete the Setup #

1. Verify & Align Your Java Version #

• First, check your current Java version in the terminal:

  java -version
  

• If the output isn't Java 8 (e.g., Java 7 or a newer version), install Java 8 (AdoptOpenJDK or Oracle JDK 8 work best for this setup).
• Set Java 8 as your default by adding this line to your ~/.bash_profile (replace /path/to/java8 with your actual installation path):

  export JAVA_HOME=/path/to/java8
  

• Refresh your terminal session with source ~/.bash_profile to apply the change.

2. Fix Gradle Wrapper Execution #

• Ensure you're in the root directory of the TEAMMATES repo when running commands.
• If you get a "permission denied" error, grant executable rights to the wrapper:

  chmod +x gradlew
  

• Run a clean setup to eliminate cached build data:

  ./gradlew clean setupEclipse
  

3. Adjust Project Location & Permissions #

• Move your TEAMMATES clone from a system folder to your user space (e.g., ~/Documents/teammates or ~/Projects/teammates).
• Ensure you have full ownership of the project files:

  sudo chown -R $USER:$USER ~/Documents/teammates
  

4. Troubleshoot Eclipse Integration #

• After running ./gradlew setupEclipse successfully, import the project into Eclipse via:

  File > Import > Gradle > Existing Gradle Project

• If Eclipse still behaves unexpectedly, start it with the -clean flag to clear cached plugin data:

  open -a Eclipse.app --args -clean
  

• Double-check Gradle settings in Eclipse: Go to Window > Preferences > Gradle and confirm the "Gradle User Home" points to a directory you have write access to (default is ~/.gradle).

5. Address El Capitan-Specific Limitations #

• OS X El Capitan deprecated some older system APIs. Ensure you're using the latest version of the TEAMMATES master branch (pull recent updates with git pull origin master) to pick up any compatibility fixes for older macOS versions.

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