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

unable to install Lombok #2

Open
alculete opened this issue Nov 30, 2024 · 11 comments
Open

unable to install Lombok #2

alculete opened this issue Nov 30, 2024 · 11 comments
Labels
bug Something isn't working

Comments

@alculete
Copy link

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.

@Mailaender Mailaender added the bug Something isn't working label Dec 6, 2024
@Mailaender
Copy link
Contributor

What is added to the eclipse.ini on a tarball installation?

@alculete
Copy link
Author

alculete commented Dec 6, 2024

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.

image

@Mailaender
Copy link
Contributor

Does it work when you manually modify according to:

echo "To override eclipse.ini, copy the default file to '$SNAP_USER_DATA/eclipse.ini' and modify to suit."

@alculete
Copy link
Author

alculete commented Dec 6, 2024

Yes, it does. Can´t eclipse.ini be changed from 'eclipse.ini': 'usr/lib/eclipse/eclipse.ini' to 'eclipse.ini': 'home/user/snap/eclipse/eclipse.ini' where it could be written. Sorry if this doesn't make sense or it is impossible to be done, I have never packed a snap before

@Mailaender
Copy link
Contributor

Try changing $ECLIPSE_HOME/eclipse.ini as suggested in https://wiki.eclipse.org/Eclipse.ini See https://github.com/eclipse-linuxtools/eclipse-ide-snap#development on how to build snaps locally. You might need to snapcraft clean to force a fresh file system for the package build.

@alculete
Copy link
Author

alculete commented Dec 6, 2024

ok Will try and revert. Also, a reminder that eclipse 2024-12 nog running

@Mailaender
Copy link
Contributor

#5 seems to be a you problem. Maybe because you are manually controlling revisions that disabled the automatic update.

@alculete
Copy link
Author

alculete commented Dec 6, 2024

I downgraded it because it updated automatically and stopped working. Purging solved the issue

@alculete
Copy link
Author

alculete commented Dec 6, 2024

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.

@Mailaender
Copy link
Contributor

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.

@alculete
Copy link
Author

alculete commented Dec 6, 2024

The first link you provided was an issue I reported. I again with 2024-12 it is not working.
Unfortunately, I will have to refactor and manually add the boilerplate code to my code or move the compressed file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants