Eclipse.app is modified when installing plugins, invalidating code signature

[nicerloop]

• I verified I can reproduce this issue against latest Integration Build of Eclipse SDK

Steps to reproduce

From a fresh installation and clean workspace:

• install any plugin, for example Cucumber from the Eclipse Marketplace
• quit Eclipse

I tried

• launch Eclipse
  => the application cannot launch as the signature is invalidated by the plugin installed inside Eclipse.app

I expected:

• Eclipse.app to start
• plugins to be installed outside Eclipse.app

But got:

• plugins installed inside Eclipse.app
• Eclipse.app doe not start because the signature is now invalid

Tested under this environment:

• OS : macOS
• Eclipse IDE/Platform version : 2024-03

Community

• I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.

Proposed fix

According to https://help.eclipse.org/latest/topic/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html , Eclipse can be made to put plugins outside Eclipse.app by making the Eclipse.app/Contents/Eclipse folder read-only (0555).

I tried making the Eclipse.app/Contents/Eclipse folder read-only and observed the desired behaviour.

The Eclipse.app distributed should have this set by default as it impacts all macOS users.