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.
Related
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.
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 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.
I've been using Flash Builder 4.5 with Flex SDK 3.5B on Mac OS X 10.8.2 for a couple months. It hasn't been a perfect experience—the software has quite a few bugs—but in general it has been working until recently.
Our application includes two Flash Builder "projects", one of which references the other. Whenever we clone the repository, it is necessary to update the .project file of the primary project to include the new path of the secondary project.
The last thing I did before everything broke was move the folder containing the projects to a new location. As expected, when I opened Flash Builder, it complained that it couldn't find my project files, and they were all marked as inaccessible in the "Package Explorer" view. I did not remove the inaccessible projects from my workspace, but I attempted to re-import the primary project from its new location. This marked the first time I saw a dialog that has haunted me ever since:
The "Problems" view told me to refer to the error log...
...but the error log was empty!
The "Package Explorer" view didn't change (the new project wasn't listed) so I decided to just try the import again. When I selected the project directory, Flash Builder said I couldn't import it because the project was already in the workspace. "But the Package Explorer says it isn't... maybe it'll let me try again if I restart Flash Builder," I thought. I thought wrong. When I restarted, this is what I saw:
java.lang.NullPointerException
at com.adobe.flexbuilder.util.PathUtils.resolveLocaleInSourcePath(PathUtils.java:297)
at com.adobe.flexbuilder.project.actionscript.internal.ActionScriptProject.getProjectPath(ActionScriptProject.java:713)
at com.adobe.flexbuilder.project.actionscript.internal.ActionScriptProject.getSourceContainers(ActionScriptProject.java:681)
at com.adobe.flexbuilder.as.editor.ui.packageexplorer.content.FlexPackageExplorerContentManager.getSourceRoot(FlexPackageExplorerContentManager.java:644)
at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.getWorkspaceRootChildren(FlexPackageExplorerContentProvider.java:152)
at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.getChildren(FlexPackageExplorerContentProvider.java:80)
at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.inputChanged(FlexPackageExplorerContentProvider.java:449)
[...]
It couldn't even display the list of projects so I could remove the one that was causing the issue. A similar message was displayed in the "Editor" view. Deleting all of the project's files didn't help either. I was unable to fix the workspace, and the only way I could continue to use Flash Builder was by creating a new workspace.
Since then, I have tried many different things:
Reinstalled Flash Builder 4.5.
Reinstalled Flex SDK 3.5B.
Checked out a six-month-old version of the project.
Upgraded to Flash Builder 4.6.
Created a new user profile on my computer.
Tried to remove whatever trace files might have broken things:
Used Instruments to monitor all files the Flash Builder process touches.
Uninstalled Flash Builder.
Used find to locate any files that included builder or eclipse in their name.
Deleted all files found in (1) or (3) that seemed possibly related to Flash Builder.
Reinstalled Flash Builder.
Installed Flash Builder 4.5 on another Mac running Mac OS X 10.6.8.
Checked out a two-year-old version of the project with Flex SDK 3.5 on the other Mac.
Tried in a new workspace on another Mac that already had the project working in an existing workspace. (Yes, it broke when we tried to import it into the new workspace, even though it continues to work fine in the existing workspace.)
Installed Flash Builder 4.5 in a Windows 7 VM.
None have made any difference. That seems impossible.
Other members of my team have been working on this project for a couple years without running into this particular issue, yet now versions of the project from before I started appear to be broken, and even using brand new installations of Flash Builder on entirely different systems also breaks.
I contacted Adobe's phone support for help with this issue. I waited on hold for over an hour after being told it would be fifteen minutes, only to have them tell me that they no longer offer phone support for the product. (Sadly, their phone tree couldn't figure that out before I waited on hold.) However, I was told that "tier 2 email support" was available at platformt2-noida#adobe.com. I should have known better than to get my hopes up the address was invalid and my messages all bounced!
I have no idea what's going on. It seems like I must have done something else and forgotten about it, because the current situation makes no sense. Has anybody encountered this issue before? Do you have any idea what might be causing it, or what I might do to fix it?
We finally found a solution. It's rather anticlimactic.
Ignore all of the errors.
Import your project files and activate the correct SDK version in whatever order you want. If you end up with a messed up "Project Explorer" view, just close the view and reopen it, or restart Flash Builder.
Once the "Project Explorer" view is available, select your primary project and run it. It should work!
Nothing was actually permanently broken. The "Project Explorer" view may be in a temporarily unusable state if you import the primary project first, or use the wrong SDK version, but as long as you eventually fix those things then the "Project Explorer" view will also be fixed the next time it's opened.
make a backup copy of all the projects in your workspace, then delete all the files (including the hidden ones) in your workspace.
Next point Flashbuilder at the now empty workspace directory (forces it to recreate all the workspace files).
now import the project folders that you had backed up.
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)