Bug 562434 - cannot start (RCP) application on MacOS
Summary: cannot start (RCP) application on MacOS
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 4.7.0   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-23 06:45 EDT by romain Monfollet CLA
Modified: 2021-02-25 09:01 EST (History)
1 user (show)

See Also:


Attachments
located at /Applications/Papyrus.app/Contents/Info.plist (1.76 KB, text/plain)
2020-04-23 06:45 EDT, romain Monfollet CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description romain Monfollet CLA 2020-04-23 06:45:07 EDT
Created attachment 282535 [details]
located at /Applications/Papyrus.app/Contents/Info.plist

I Start the Papyrus using standard click procedure, and a popup shows:

The JVM shared library "/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/bin/../jre/lib/server/libjvm.dylib"
does not contain the JNI_CreateJavaVM symbol.

So i go on investigating

--------
I start the app using the CLI at /Applications/Papyrus.app/Contents/MacOS/papyrus

The console shows:

2020-04-23 12:36:42.608 papyrus[82671:6107864] Error loading /Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/MacOS/libjli.dylib:  dlopen(/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/MacOS/libjli.dylib, 265): no suitable image found.  Did find:
	/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/MacOS/libjli.dylib: code signature in (/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/MacOS/libjli.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.

at the same time, the Papyrus popup says: 
The JVM shared library "/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/bin/../jre/lib/server/libjvm.dylib"
does not contain the JNI_CreateJavaVM symbol.
Comment 1 Pauline Deville CLA 2021-02-25 09:01:16 EST
I confirm the bug.