Open mdaloia opened 1 month ago
By the way, if you use the absolute path pointing to the same bin/java
executable it works ok.
By the way, if you use the absolute path pointing to the same
bin/java
executable it works ok.
Do you think you can provide a PR with a proposed solution? But since I cannot help at all with Mac, maybe @sravanlakkimsetti or @Phillipus can help?
I'm sorry, but I don't know about ObjectiveC coding nor I have the proper environment.... maybe the original author could help on this...
@subyssurendran666 could you take a look at it?
Thanks in advance
@mdaloia Sure, I'll check this issue and get back to you.
@subyssurendran666 Did you have time to look at it?
It seems that this change https://github.com/eclipse-equinox/equinox/commit/19582c5fc50a7946b8e642d26740daae8ba32197 introduced with PR https://github.com/eclipse-equinox/equinox/pull/481 on the native macOS launcher of Eclipse 4.31 breaks a previously working scenario (until 4.30) where the JVM used to launch Eclipse has a macOS layout (as it has Temurin) and you reference it under
-vm
ineclipse.ini
with a relative path tobin/java
Error:
Steps to reproduce
Download Eclipse 4.31
Open it once (to check that it work with the embedded JustJ JRE and so the macOS does the Notarization Gatekeeper check, otherwise if you modify it directly it will say that it is damaged).
Download Adoptium Temurin JRE 17 for macOS (https://adoptium.net/temurin/releases/ )
Extract the JRE at the same level of the![image](https://github.com/eclipse-equinox/equinox/assets/1738654/e10afbc6-bf23-45bd-a158-64d0dfafb974)
Eclipse.app
Modify the
-vm
arg ofEclipse.app/Contents/Eclipse/eclipse.ini
to:Execute
Eclipse.app
Workaround
Use: