megit icon indicating copy to clipboard operation
megit copied to clipboard

Can't start the zip attached to the 0.0.2 release on MacOS

Open jmini opened this issue 4 years ago • 6 comments

Go to the 0.0.2 (2020-12) page.

I have downloaded the com.eclipsesource.megit-macosx.cocoa.x86_64.zip (link)

I have unzipped the file (standard macOS utility) I get this error dialog when I start the decompressed "Eclipse.app" file:

Error dialog: Eclipse is damaged and can't be opened. You should move it to the Bin.

jmini avatar Feb 18 '21 20:02 jmini

I've never tested the MacOS build (I don't have one) and I'm not sure what's wrong, unfortunately. :/

planger avatar Feb 19 '21 08:02 planger

The local build is working:

With Java 11 on the path:

$ java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)

I can run:

mvn verify -f com.eclipsesource.megit.parent/pom.xml

And open the generated Eclipse.app.

  1. Either unzip:
com.eclipsesource.megit.product/target/products/com.eclipsesource.megit-macosx.cocoa.x86_64.zip

and start the Eclipse.app extracted from the zip.

  1. Or start:
com.eclipsesource.megit.product/target/products/com.eclipsesource.megit/macosx/cocoa/x86_64/Eclipse.app

jmini avatar Feb 19 '21 17:02 jmini

One note that you need to know (standard for all RCP app including Eclipse IDE itself):

You should have Java 11 which is not the default on my mac.

Either you start with open <path to Eclipse.app> from a Terminal where Java 11 is the default version.

Or you edit the file megit.ini (inside Eclipse.app with right click "Show Package Contents" and edit the file Eclipse.app/Contents/Eclipse/megit.ini) to add the -vm entry with the path pointing to your Java 11 installation. See https://wiki.eclipse.org/Eclipse.ini

jmini avatar Feb 19 '21 17:02 jmini

I also cannot test it on MacOS (running on Linux).

Could you please compare the content of downloaded Eclipse.app and an Eclipse.app from a build? I'd say that if both of them can be executed from terminal with proper java then we are somehow OK. If the downloaded Eclipse.app cannot be run that would mean that the package is corrupted.

Thanks for your input at least we have some suggestion how to run it on MacOS alternatively.

jirkafm avatar Mar 10 '21 21:03 jirkafm

Workaround (tested on macOS Big Sur):

sudo xattr -rd com.apple.quarantine ./Eclipse.app

cristian-anita avatar May 18 '21 16:05 cristian-anita

See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=398450

planger avatar Jan 25 '23 13:01 planger