Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Installation via jar problematic on Mac Sierra and later #2631

Open
Marcuse7 opened this issue Oct 28, 2020 · 3 comments
Open

[BUG] Installation via jar problematic on Mac Sierra and later #2631

Marcuse7 opened this issue Oct 28, 2020 · 3 comments
Labels
parked Without further feedback this bug cannot be processed. If no feedback is provided, we close these.

Comments

@Marcuse7
Copy link

The documentation for Eclipse states "Double-click lombok.jar". On a Mac with macOS "Sierra" or later, the Apple Gatekeeper will block this action as the jar is unsigned.

Please include at least one workaround in the documentation, such as using java -jar ~/Downloads/lombok.jar from terminal.

Otherwise, please consider signing the jar with an inexpensive certificate such as Comodo (you could use Patreon to raise the money for that).

@rspilker
Copy link
Collaborator

Not sure if signing using such a certificate would solve the problem.

Does right-clicking the jar and selecting "Open" allow you to run the code anyway?

We are migrating to using the Eclipse plug-in system P2 to install Lombok into your Eclipse.

@rspilker rspilker added the parked Without further feedback this bug cannot be processed. If no feedback is provided, we close these. label Oct 29, 2020
@rzwitserloot
Copy link
Collaborator

It's not so much about the cost, it's about the maintenance burden of figuring this stuff out. From my limited understanding of what gatekeeper is, signing it with a comodo cert, or the concept of 'a signed jar' has no effect whatsoever on what gatekeeper would do.

@rzwitserloot
Copy link
Collaborator

Done some more research and it looks like apple made it impossible to sign a jar such that it is no longer stopped by gatekeeper or whatever that is.

I'm going to give it a week or two for somebody to explain to how to fix this problem, and if nothing is forthcoming, this issue will be closed with no action. A java developer using a mac will know this (or if they don't, the fact that the lombok instructions don't spell it out is the least of their problems).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
parked Without further feedback this bug cannot be processed. If no feedback is provided, we close these.
Projects
None yet
Development

No branches or pull requests

3 participants