I have a problem with my eclipse. Whenever I go to the Install Software screen and put in a an update site, the screen shows nothing but when I click on the screen where I can select plugins they're there and I can actually go on to install the plugins.
I actually saw the plugins showing the first time I used it and then I got this error:
"A handler conflict occurred. This may
disable some commands"
eclipse.buildId=M20090917-0800
java.version=1.6.0_15 java.vendor=Sun
Microsystems Inc. BootLoader
constants: OS=linux, ARCH=x86, WS=gtk,
NL=en_PH Framework arguments:
-product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws
gtk -arch x86 -product
org.eclipse.epp.package.jee.product
Warning Sun Dec 27 14:13:49 PHT 2009
Conflict for
'org.eclipse.wst.jsdt.ui.edit.text.java.open.editor':HandlerActivation
(commandId=org.eclipse.wst.jsdt.ui.edit.text.java.open.editor,
handler=ActionHandler(org.eclipse.wst.jsdt.ui.actions.OpenAction#8eec22),
expression=AndExpression(AndExpression(org.eclipse.ui.SubActionBars$1#12f8a71,
ActivePartExpression(org.eclipse.ui.navigator.resources.ProjectExplorer#1e8b957)),
WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#270fc4)),
sourcePriority=1064961)
HandlerActivation(commandId=org.eclipse.wst.jsdt.ui.edit.text.java.open.editor,
handler=ActionHandler(org.eclipse.wst.jsdt.ui.actions.OpenAction#8eec22),
expression=AndExpression(AndExpression(org.eclipse.ui.SubActionBars$1#12f8a71,
ActivePartExpression(org.eclipse.ui.navigator.resources.ProjectExplorer#1e8b957))
,WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow#270fc4)),
sourcePriority=1064961)
After reading items in this post I checked if deleting the .metadata folder fixed the situation. It fixed the problem but I lost my workspace settings. In order to fix this without losing your workspace settings you must delete only this file:
${YOUR_WORKSPACE_FOLDER}/.metadata/.plugins/org.eclipse.equinox.p2.ui/dialog_settings.xml
ggolebio had the right idea, and I'm assuming he got the information from https://bugs.eclipse.org/bugs/show_bug.cgi?id=324729
Rather than deleting the file do the following:
edit ${YOUR_WORKSPACE_FOLDER}/.metadata/.plugins/org.eclipse.equinox.p2.ui/dialog_settings.xml
set the AvailableNameColumnWidth to 420
set the AvailableVersionColumnWidth to 140.
Restart eclipse
profit
This will not kill your workspace customizations like other solutions do.
Deleting the .metadata folder fixed it for me. Not sure of the cause but it was around the time I upgraded to Juno
I had this problem too. First try creating a new workspace, and see if you still have the same problem. If so, then try deleting the .metadata directory from the corrupted workspace.
$ cd ~/<your-eclipse-corrupted-workspace>
$ rm -r .metadata/
I made the mistake of closing the "install new software" window after trying to filter "all available downloads" which was taking to long. That triggered the problem. I tried reinstalling. I uninstalled and reinstalled. I deleted my ~/.eclipse folder. That made eclipse start in the default workspace, ~/workspace which suddenly didn't have the problem. That's what made me realize that my problem was a corrupted workspace. As soon as I deleted the .metadata folder the problem disappeared.
There are bug reports on LaunchPad and eclipse.
Try installing the Eclipse package from Synaptic; it's been updated to the latest version just recently (though you may need to enable more recent updates from the Software Sources dialog or something).
Makes sure you install version 3.5.1-0ubuntu7 or later from Synaptic. I'm not in Ubuntu right now to check, but this bug has been fixed in that version and later. See this bug report.
If for some reason you can't do that, then do the workaround here.
They did not fix the issue. The solution of ggolebio, today 16 june 2015, is still working.
sudo rm /home/USERNAME/.workspace/.metadata/.plugins/org.eclipse.equinox.p2.ui/dialog_settings.xml
Sounds like a bug somewhere. This could be specific to your OS or environment.
Start by checking the Error Log view (to show it, use the Window -> Show View option. See if you are getting any exceptions there.
To eliminate workspace issues: Try with a new workspace (simply switch to a new workspace, you can always switch back later).
To eliminate issues with your specific installation: Try with a clean Eclipse install. You can download a new installation from eclipse.org and install it in a different directory.
Search for existing bugs in Eclipse Bugzilla. If there are none, report yours. Attaching your configuration to the bug report might help (under About Eclipse -> Installation Details -> Configuration, copy and save to a text file).
Related
After upgrading to Big Sur this weekend, my older version of Eclipse (Mars) I use for a specific project cannot be started. I did the suggestion of updating the vm in /Applications/Eclipse.app/Contents/Info.plist -
Not able to run Eclipse on macOS Big Sur
Now I am getting this error:
!MESSAGE Could not read version file /Users/lorapowell/Documents/MARs
workspace/.metadata/version.ini STACK 0 java.io.FileNotFoundException:
/Users/lorapowell/Documents/MARs workspace/.metadata/version.ini
(Operation not permitted)
The file is there and has date (around when I did the upgrade?)
#Sat Jan 16 23:42:07 MST 2021
org.eclipse.core.runtime=2
org.eclipse.platform=4.5.2.v20160212-1500
My newer version of Eclipse is working fine.
You'll need to ensure you're running a more recent version of Eclipse than that.
The problem specifically shown here is because the Documents folder needs to be opted in to allow access from programs. This can be found in System Preferences, in the Security & Privacy preference pane on the Privacy tab.
You might find that Eclipse is showing in there with a Desktop folder without a checkmark. If that's the case, add the checkmark, then re-launch the application.
After moving the zip files for the referenced build path libraries to under my /Users/profilename and re-expanding them, then updating the .classpath for these, cleaning and rebuilding as well as closing and reopening Eclipse a few times, I got things to sort themselves out. Build works. Older eclipse, but it allows me to connect to my cmvc source project.
So very weird, first time I ever saw this, problem install STS version 3.8.3-release on Macbook Pro running mac osSerria v10.12.3. Here's what's I do:
Down load the STS distro spring-tool-suite-3.8.3.RELEASE-e4.6.2-macosx-cocoa-x86_64.tar.gz from https://spring.io/tools/sts/all
Move the zip file to my Applications folder
Extract the distro. This creates the sts-bundle folder, and; under that, the STS programs exists.
I then just run STS. Since this is a first-time I do get the pop-up for selecting the default workspace. I change it to where I want the workspace and I also check the "Don't ask again".
Install some plug-ins, do work, everything is normal.
I can exit the app throughout the day and, when I go back in all is cool.
Now...the problem...
1. Shutdown the laptop for the day. This is to say I select Apple->Shut Down..
2. The next day I come in, boot-up the laptop.
3. Open Applications and select STS and run STS.
At this point, I get the "Select default workspace" popup again...all my preferences, and installed plug-ins are forgotten, and it's like I'm running the application again for the first time?? It is especially weird that any plug-ins I installed are also forgotten??
I have completely removed STS, and reinstalled several times and it is pretty consistent. Also, I have installed STS on several iMac desktops without issue. This smells like a permissions problem but not errors just...all customized preferences are simply gone.
Any ideas would be greatly appreciated.
The answer to this is App Translocation, which is done by OSX. For details, take a look here, we analyzed this in detail:
STS.app on Mac 10.12.1 always creates a new org.springsource.sts folder in .eclipse
I've downloaded and installed STS 3.8.2 on my Mac (10.12.1). Each time the STS.app file is launched, it creates a new org.springsource.sts_3.8.2.RELEASE_########_macosx_cocoa_x86_64 folder under the hidden .eclipse folder (the hashes are there because I have MANY of the same folder with the numbers in the hash area being the only difference). In doing so, the default workspace and all plugins I installed the last time it was running are wiped out (because they exist in the previous #### folder).
I've tried installing the previous 3.8.1 and 3.8.0 version, but they are doing the same thing. My previous STS install started at 3.7 and has been upgraded to 3.8.1, but will not update anymore because of update errors that I can't seem to fix (none of the StackOverflow "fixes" have worked for me).
Is there a way to have STS not create a new folder (instance) in the .eclipse folder each time it launches? If so, how?
This got reported to STS and is documented here:
https://issuetracker.springsource.com/browse/STS-4406
The corresponding bug at Eclipse is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=507328
To cut a long story short:
This is caused by macOS Sierra Gatekeeper App Translocation, a security feature that moves the app into a private read-only location for security reasons. Therefore Eclipse/STS creates a folder for its configuration in that location that you described above.
Since macOS Sierra does the app translocation again after every restart, Eclipse/STS doesn't know anything about the "old" configuration area anymore and creates a new one. As far as I can see, there is no way for Eclipse/STS to distinguish between a separate install and a newly translocated app... :-(
The workaround is:
A) Move STS.app into a different location on your disc after
unpacking the tar.gz archive (using the Finder, not the command
line). If you move it to "Applications", for example, everything
works as before (no app translocation happens in that case).
B) You could also start Eclipse/STS by clicking on the Executable (in
STS.app/Contents/MacOS). That also doesn't cause app translocation
and therefore everything is fine.
As this bug — alternatively unfortunate side-effect of Apple security measures — still exists in STS 3.9.8 (I assume also in 3.9.9) and the Eclipse bug report in the previous answer is closed as a duplicate of Workspace Preferences Do Not Persist on MacOS Sierra that, while being marked as "solved, actually in itself actually do not solve this dislocation issue — in that moving the app to /Applications or having a signed DMG, both making no difference — the info missing is that one can turn off App Dislocation on an app by app basis by using the "xattr" command in the Terminal, that works upon extended file attributes.
Use the command
sudo xattr -r -d com.apple.quarantine /Applications/sts.app
where -r makes the command recursive for all app contents (macOS apps being folders) and -d deletes the particular attribute at the given path.
To verify a successful result simply run
sudo xattr /Applications/sts.app
The successful result you want is a new prompt line. If you get "quarantine" on there you were not successful.
Note that, I could only test this in macOS 10.12.6
My Eclipse was getting slower and slower over time. Tips I found on the Internet did not help.
What I did is completely deleted my workspace, created new one and reimported all my projects into the new workspace and this really made the difference.
So my question is whether it's possible to perform this workspace clean-up without deleting and recreating workspace...
Maybe there is some cache in workspace which is getting big? Any ideas?
Thank you!
Eclipse keeps track of all changes in local history. That might introduce slowdown over time.
Local history is located at .metadata/.plugins/org.eclipse.core.resources/.history.
Not sure about newer versions of eclipse, but in 3.1 settings in
Preferences->General->Workspace->Local history
did not work for me. I had it set by default to 7 days but files were kept for 4 years. And I guess other people here had the same issue.
For me it helped to remove history files manually from
.metadata/.plugins/org.eclipse.core.resources/.history.
I use RAD 7.5 (which is based off of Eclipse 3.4). I found several of my projects had millions of history files, all older than 7 days, and mostly the same dummy MANIFEST.MF file (39 bytes).
I discovered this when I tried to delete an old project with Windows Explorer. After 12 hours, Windows Explorer reported that it had recycled 3.5 million files, and was still working.
I found the only way to remove the workspace was to open a Command Window, CD to
<project>\.metadata\.plugins\org.eclipse.core.resources\.history
then type
DEL *.* /s/q
Even this took the better part of an hour.
Try running eclipse from command prompt with
eclipse.exe -clean
More http://www.myeclipseide.com/PNphpBB2-viewtopic-t-10280.html
Sometimes due to Physical Memory issue it cant build the workspace.
So To remove Memory issues update #
eclipse.ini
file as below
-Xms512m
-Xmx1024m
-XX:MaxPermSize=1024m
--launcher.XXMaxPermSize 1024m
I just solve the problem by deleting all stuffs inside eclipse's directory OPTReplica. after that, re-stat eclipse, for me it helps.
Eclipse is programmed as a filebomb, and it causes a large variety of problem, evben on modern robust filesystem. Problem can goes from large waste of diskspace for nothing to preventing your OS to boot if your workspace is on your OS partition. Eclipse is programmed as a filebomb.
The cleanup mechanism in eclipse doesn't work, so the only viable option is to frequently cleanup your workspace by hand at regular interval, or to add your cleanup code to a sh file that does it before launching eclipse.
An other option will be to introduce the eclipse developpers to the fabulous world of databases that produce faster to run and easier to write code. Sadly a rhumor says that they will shot on sight everyone that pronounce the words "sqlite" or "jdbc", and will sacrifice virgind every sunday to the all-mighty-god-of-filebombs.
Does somebody know how to recover a never-starting eclipse when the error "org.eclipse.swt.SWTError: Item not added" is raising againg and again?
I'm using WebSphere Studio Site Developer (Windows) 5.1.0
The only stack trace in the .metadata/log file is:
SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 sep 17, 2008 16:39:00.564
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException: java.lang.reflect.InvocationTargetException: org.eclipse.swt.SWTError: Item not added
at java.lang.Throwable.<init>(Throwable.java)
at java.lang.Throwable.<init>(Throwable.java)
at org.eclipse.swt.SWTError.<init>(SWTError.java:82)
at org.eclipse.swt.SWTError.<init>(SWTError.java:71)
at org.eclipse.swt.SWT.error(SWT.java:2358)
at org.eclipse.swt.SWT.error(SWT.java:2262)
at org.eclipse.swt.widgets.Widget.error(Widget.java:385)
at org.eclipse.swt.widgets.Menu.createItem(Menu.java:464)
at org.eclipse.swt.widgets.MenuItem.<init>(MenuItem.java:77)
at org.eclipse.ui.internal.AcceleratorMenu.setAccelerators(AcceleratorMenu.java:177)
at org.eclipse.ui.internal.WWinKeyBindingService.updateAccelerators(WWinKeyBindingService.java:316)
at org.eclipse.ui.internal.WWinKeyBindingService.clear(WWinKeyBindingService.java:175)
at org.eclipse.ui.internal.WWinKeyBindingService.update(WWinKeyBindingService.java:267)
at org.eclipse.ui.internal.WWinKeyBindingService$1.partActivated(WWinKeyBindingService.java:107)
at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:49)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:47)
at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:1180)
at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:1833)
at org.eclipse.ui.internal.WorkbenchWindow$7.run(WorkbenchWindow.java:1496)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:1483)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1363)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1263)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1223)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1141)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState(Workbench.java:1093)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:870)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1373)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.AccessibleObject.invokeL(AccessibleObject.java:207)
at java.lang.reflect.Method.invoke(Method.java:271)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
I had exactly the same problem. I did not restart my machine, and just used "eclipse -clean" to start eclipse. It worked. Thanks Jon for the hint.
Does restarting your computer resolve the problem with being able to open the workspace? There is a forum post (http://forums.sun.com/thread.jspa?messageID=3131484#3131484) that describes a similar problem with an identical stack trace as the one shown above. In the post, the author mentions that their machine was low on resources (they did not specify what type of resources were running low).
If restarting your computer does not work, you may want to try starting eclipse with the clean option:
eclipse -clean
The clean option will clean out any caches that Eclipse has created.
If all else fails, you may want to open a bug for this problem at https://bugs.eclipse.org/bugs/. Including a copy of your workspace (if possible), and including the stack trace in the bug would be helpful information for the person trying to diagnose the problem.
Good Luck!
Well, some things you can try are:
Delete workspace .metadata dir. Obviously you will lose your workbench configuration.
Rename your .metadata dir. Start Eclipse, and you will have a new .metadata dir. Close Eclipse, delete the new dir, and rename back the original dir. It sometimes works.
HI,
Check the task manager, whether any java process(java.exe or javaw.exe) running even after the closing of workbench. Kill those processes. You will get this error resolved
For me, I think this has something to do with my dual monitor setup and Actual Multiple Monitors that I have installed. I disabled that and the problem is gone.
This worked when I moved the eclipse.ini from the eclipse install folder (where .exe is present). I ran into this problem when I was trying to increase the heap size in the eclipse.ini file (although I had seen this error earlier)