Wrong architecture config on Apple Silicon

[pradeepvenkataraman]

Relevance Confirmation

• I confirmed that this is not an issue with the Eclipse JDT Language Server itself

What happened?

JDT LS is launched with config_mac (Intel) instead of config_mac_arm on Apple Silicon (arm64). Both directories exist in the JDT LS installation but the wrong one is selected.

• Launch arg used: config_mac
• Should be: config_mac_arm
• Machine: Apple Silicon (arm64)
• Extension version: 6.8.17
• JDT LS version: 1.58.0-202604151538

What did you expect to happen?

I expect the proxy to launch using config_mac_arm when running on Apple Silicon Mac

/Users/pradeepbhargav/Library/Application Support/Zed/extensions/work/java/proxy-bin/v6.8.17/java-lsp-proxy /Users/pradeepbhargav/Library/Application Support/Zed/extensions/work/java /usr/bin/java -Declipse.application=org.eclipse.jdt.ls.core.id1 -Dosgi.bundles.defaultStartLevel=4 -Declipse.product=org.eclipse.jdt.ls.core.product -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area=/Users/pradeepbhargav/Library/Application Support/Zed/extensions/work/java/jdtls/jdt-language-server-1.58.0-202604151538/config_mac -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true -Djava.import.generatesMetadataFilesAtProjectRoot=false -Xms1G --add-modules=ALL-SYSTEM --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED -javaagent:/Users/pradeepbhargav/Library/Application Support/Zed/extensions/work/java/lombok/lombok-1.18.46.jar -jar /Users/pradeepbhargav/Library/Application Support/Zed/extensions/work/java/jdtls/jdt-language-server-1.58.0-202604151538/plugins/org.eclipse.equinox.launcher_1.7.100.v20251111-0406.jar -data /Users/pradeepbhargav/Library/Caches/jdtls-e8c3188a3

Environment

Zed: v1.2.2
Platform: macOS 26.5
Java: Oracle GraalVM 25.0.3+9.1

[tartarughina]

@pradeepvenkataraman thanks for raising the concern. Our launch script is a 1:1 copy of the one vended by jdtls.

Fun fact, we have a comment specifically about this but no one has ever really looked into it.

// Note: JDTLS also provides config_linux_arm and config_mac_arm (and others),
// but does not use them in their own launch script. It may be worth investigating if we should use them when appropriate.

I'll see whether there are contraindications adopting it or whether it is safe to make it the default.