-
Notifications
You must be signed in to change notification settings - Fork 2
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
unable to install Lombok #2
Comments
What is added to the |
it adds a javaagent at the end of the file. if there is no write permission you can´t change the file maybe eclipse.ini could be put on a different location, maybe on ~/snap/eclipse. This is done when you install the addon. In this case the Lombok addon, but I think it might work the same way as other addons installed through Install new Software. |
Does it work when you manually modify according to:
|
Yes, it does. Can´t eclipse.ini be changed from |
Try changing |
ok Will try and revert. Also, a reminder that eclipse 2024-12 nog running |
#5 seems to be a you problem. Maybe because you are manually controlling revisions that disabled the automatic update. |
I downgraded it because it updated automatically and stopped working. Purging solved the issue |
Hi @Mailaender I know what caused the issue. When the IDE is updated the eclipse.ini on /home/user/snap/... is not updated and the plugins listed there became outdated comparing to the one int he original eclipse.ini. One disadvantage of overriding the default eclipse.ini. |
It is definitely not an optimal solution to the read-only file system problem that was inherited from @snapcrafters as stated in snapcrafters/eclipse#74 and projectlombok/lombok#2720 but I don't have a better solution at hand. |
The first link you provided was an issue I reported. I again with 2024-12 it is not working. |
Unable to install Lombok or any other plugin not in the store through Help > Install New Software.
It finished installing, but after that, it restarted, and nothing was installed. This might be related to eclipse.ini not being writable.
The text was updated successfully, but these errors were encountered: