I used Eclipse PDT Mars on 2010 Macbook for years - no problem.
I got a 2013 Macbook with latest OS. Transferred everything with migration assistant.
After OS update, I updated Eclipse - because Mars crashed every time I pressed delete with highlighted text on new OS.
I used default startup options for Eclipse 2020.
Sadly - no PHP content assist after update to Eclipse 2020 - "No default proposals."
Errors:
!ENTRY org.eclipse.jface.text 4 0 2020-04-11 00:12:22.371
!MESSAGE Unexpected runtime error while computing a text hover
!STACK 0
java.nio.channels.OverlappingFileLockException
Note: OverlappingFileLockException is repeated many times in log files.
How can I get my content assist to work? I tried changing settings, deleting work spaces.
Thank you.
Thank you #howlger
I reinstalled and created new workspace.
PHP content assist worked - and log has no errors - after I put empty workspace on main disk instead of external flash drive.
I think MacOS Catalina added too much security for external drives.
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.
I'm running Ubuntu 12.04. After running "check for updates", one of the listed updates was Eclipse Platform ==> 3.7.2, which I couldn't select (white plug type icon). A conflict dependency was described, something to do with Java Development Tools, I think. Anyway, I force selected everything (which included the Eclipse Platform) and then manually deselected every other option except the Eclipse Platform. I was then able to go ahead with the update just for that option.
The update seemed to be going fine, but ultimately ended up with an error, which was that a file could not be deleted successfully (I believe it was /usr/lib/eclipse/.eclipse or something similar). After following some advice, I ran sudo chown -R $USER:$USER /usr/lib/eclipse /usr/share/eclipse and then repeated the update process done previously, which worked.
After restarting Eclipse, all my plug-ins appear to be missing. Eclipse looks like it's completely stripped down. In the help menu, there's no longer any "Check for updates" option. Although in the installation details, the plug-ins are still listed.
I tried resetting ownership of the eclipse directories back to root, but it doesn't change anything. I've looked around at various bug reports and forums etc. but I'm not sure what to do. Can anyone help me?
Error Log:
Error
Sun Jan 19 11:50:37 GMT 2014
Error creating feature
"file:/usr/lib/eclipse/features/org.eclipse.equinox.p2.user.ui_2.1.2.R37x_v20110815-1155-
6-Bk8pYWZz0qUTX5I15GZWwbXkrl/".
[/usr/lib/eclipse/features/org.eclipse.equinox.p2.user.ui_2.1.2.R37x_v20110815-1155-6-
Bk8pYWZz0qUTX5I15GZWwbXkrl/feature.xml (No such file or directory)]
... followed by another similar entry, followed by:
Error
Sun Jan 19 11:37:42 GMT 2014
FrameworkEvent ERROR
org.osgi.framework.BundleException: The bundle
"org.eclipse.equinox.p2.reconciler.dropins_1.1.100.dist [80]" could not be resolved.
Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.p2.touchpoint.eclipse;
bundle-version="1.0.0"
... followed by:
Error
Sun Jan 19 11:37:42 GMT 2014
Bundle reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-
1438.jar#1:start not found.
I am running ubuntu 12.04 64 bit, I have set up FB4Linux (FlashBuilder for Linux) and installed the »flash-installer« installer plugin via »apt-get«. I downloaded the latest version of the plugin-debugger from adobe and followed the install instructions from the included README.txt file. Running eclipse (Version: 3.7.2, Build id: I20110613-1736), creating a new as3 project works, build works, everything fine, I can start the debugger and step through the code BUT after a while the debugger just disconnects and stops. No error, no crashes, debug session just over.
Any Ideas?
.log
about:plugins:
Flash - Version: 11.2 r202
Shockwave Flash 11.2 r202
I think , this is happenning more fequently due the enhanced breakpoint listener support in eclipse.When a breakpoint is removed, it is trying to notify its "breakpoint specific" listeners, which were stored in the breakpoint. Of course, this will not work since the underlying marker has been deleted. but things will happen after removing break point. so one way to resolve this problem is to try to un-select
Window > Preferences > Java > Debug : Suspend execution on uncaught exceptions
may this will help you!!
The solution to this issue occurred as side effect after I applied the changes from the answer of this question. When I tried to set the compiler options to target version 11.2, which is actually installed on my system errors occurred because their were files missing in the sdk folder (which are the described changes) and I could only develop for version 11.1. Kind of wired but the update of the sdk made the debugger run stable.
Periodically (during autosave) and at close i get:
Problems saving workspace
(X) Problems occurred while trying to save the state of the workbench.
Details >>
Could not write metadata for '/projectname'.
encoded string too long: 123456 bytes
Can't find a reason or solution for this using the usual means. Any ideas how to fix?
THis is using eclipse 3.4 (Ganymede)
It should relate to a bug in DataOuputStream that it cannot writeUTF with longer then 65535 utflen.
If I were you, I will try to find a way to reduce the data size, and I will submit bug report to Eclipse and JRE.
Started having the same issues under Vista x64. The latest JRE appears to not have the same DataOuputStream limitation so installing it fixes the annoyance.
An observation I've made about these occurrences for me is that they only occur on newly created projects during the same Eclipse session that I created the project. Once I restart Eclipse, I don't see the issue again until the next time I create a new project.
Has anyone else noticed this about the occurrences of the error for them?
It's not a write permissions or disk-space issue. I'm getting the same problem on Eclipse 3.5 M4. No troubles with 3.4.1.
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)