I am sure most Eclipse users have run into some "funny" (as in, this milk tastes funny, not funny haha) issues from time to time, namely:
Extremely slow start up times.
Unable to open any editor.
A resource already exists on disk when building.
These will probably be more of an issue for users that install a large amount of plugins or products like MyEclipseIDE.
I was having some of the issues I mentioned above, went searching for a bit and found and Eclipse option:
It looks like this tells Eclipse to erase and rebuild it's internal plugin cache which in turn sorts out some versioning / state issues. You only need to run it once so the option can be removed after the workspace restart.
So for MyEclipseIDE I added it to myeclipse.ini just before the -vm option.
Closed and opened Eclipse... and both issues were solved. /cheer
If you are just using standard Eclipse, you can place it in your eclipse.ini
I make no claim to be a "computer scientist" or a software "engineer", those titles alone can spark some debate, I regar...
This series of posts will be about me getting to grips with JBoss Drools . The reasoning behind it is: SAP bought out my company's curre...
I saw an article (well more of a rant) the other day, by Rob Williams Brain Drain in enterprise Dev . I have to say, I do agree with some o...
I recently finished 97 Things every programmer should know . Well to be completely honest I did skim over a couple of the 97, but all and al...
I have over the last couple years used EhCache either via Spring (with AOP) or having it configured as hibernates' cache. I have never ...