使用Buckminster更新p2站点时遇IllegalArgumentException错误求助

Hey there! Let's work through this frustrating Buckminster error you're hitting. That IllegalArgumentException about case variants of awt.toolkit usually pops up when there are duplicate system properties with the same name but different capitalization floating around in your environment or project config. Here are some actionable steps to resolve it:

1. Hunt for Duplicate System Properties #

First, check if there are conflicting awt.toolkit properties in your Eclipse or JVM setup:

• Open your Eclipse eclipse.ini file (found in your Eclipse installation directory) and scan for lines like -Dawt.toolkit=... or -DAWT.Toolkit=.... If both exist, delete one and keep the lowercase version (standard convention).
• Go to Window > Preferences > Java > Installed JREs, select the JRE you're using for the project, click Edit, and check the Default VM arguments field for any duplicate or case-variant awt.toolkit entries. Remove duplicates and standardize to lowercase.
• Also verify your system environment variables (outside Eclipse) don't have both AWT_TOOLKIT and awt_toolkit set—these can sometimes leak into the JVM.

2. Audit Buckminster Configuration Files #

Double-check your project's Buckminster-related files for conflicting property definitions:

• Open the buckminster.properties file in your targetplatform.feature project. Look for any lines setting awt.toolkit (or case variants like AWT.Toolkit). If you find multiple entries or mixed case, keep only one using the lowercase key.
• If you have other Buckminster config files (like .cspec or .mspec), scan those too for similar conflicts.

3. Clean Buckminster Cache and Rebuild #

Buckminster might be holding onto outdated cached properties. Try a full clean:

• Right-click your targetplatform.feature project, select Buckminster > Clean.
• Restart Eclipse entirely, then re-load your target platform (Window > Preferences > Plug-in Development > Target Platform, select your platform and click Reload).
• Try running the site.p2 action again after this.

4. Verify Target Platform Integrity #

It's possible your remote target platform has components that are setting conflicting awt.toolkit properties:

• Open your target platform definition file (.target) in targetplatform.source, and review the included features/plugins. Look for any that might modify system properties (rare, but possible for UI-related plugins).
• Try re-downloading the remote target platform fresh to ensure you have the latest, uncorrupted version.

5. Force a Unified Property via VM Arguments #

If all else fails, explicitly set the awt.toolkit property when invoking the site.p2 action to override any conflicts:

• Right-click your project, select Buckminster > Invoke action... > site.p2.
• In the dialog that opens, switch to the Arguments tab.
• In the VM Arguments field, add the appropriate value for your OS:
  • Windows: -Dawt.toolkit=sun.awt.windows.WToolkit
  • Linux: -Dawt.toolkit=sun.awt.X11.XToolkit
  • macOS: -Dawt.toolkit=apple.awt.CToolkit
• Click Run to execute the action with this forced property.

Hopefully one of these steps gets past that awt.toolkit conflict and lets your site.p2 action run successfully!

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