-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bundle Pool Cleanup Agent makes Eclipse un-launchable #109
Comments
Yes, it's not really been tested in a very long time and I'd personally be a bit (very) scared to use it on my pool that supports around 100 installations. It's not an easy thing to test and debug either. Sorry about that. 😢 |
Perhaps disable it then for the meantime. |
Yes, or at the very least, a big warning, warning, warning to create a backup in the likely case of overly aggressive removals. I'll try to find some time for testing and failing to find an obvious problem that can be fixed, take some other remedial action, e.g., creating a backup folder with the deleted content. Not sure... |
That worries me a bit... |
I did test it since I wrote my comment and it worked fine for me, on a test user folder. So I'm not really sure what problem there might be... |
Installer version: 1.34.0 Build 753
After installing Eclipse Platform 4.33 with bundles enabled, Eclipse can be launched. If you then go to Bundle Pools > Cleanup Agent and clean "unnecessary" items, Eclipse doesn't launch anymore with the message:
The cleaner is cleaning too much apparently.
The text was updated successfully, but these errors were encountered: