I want to lower the version of ChromeDriver in my eclipse. For that I want to delete the Chromedriver from Eclipse. However when I try to delete the Chromedriver. I got an error "An exception have been caught while processing refractoring delete" Reason: Problems encountered while deleting resources. I don't know how to change the version of my ChromeDriver now.And may I know why this happens, What should I do know?(I am not able to replace Chromedriver of different versions as well in eclipse)
Sorry, i am very late.
i just realized the solution by miyself about the same problem. If you have copied ChormeDriver into your package, then you have delete all instances of Chormedriver on the memory. To do that, you need to click on Task Manager (Cntrl+Alt+Del) -> Select Task Manager and search for all Chorme Driver(s) and delete these tasks from process on Task Manager. Before you do the above step, close Chrome Browser. Once you delete all those tasks from Task Manager, then go to Eclipse and delete ChromeDriver from pacakge.
Restart the machine
From eclipse open system explorer
find chromedriver.exe and replace the chromedriver.exe with older or newer version.
Related
i got got SessionNotCreatedException, so i installed new version of chrome driver, i pressed delete on old path then eror msg came.
can any one suggest me the way out.
#Pratheeksha Nayak, this happens as your old chromedriver.exe is still in use. So restarting the machine or deleting the chromedriver.exe process from the task manager should resolve this.
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 have had all sorts of bizarre errors, like the one in the title, happen when I am using the Android SDK and AVD Manager with Eclipse. Generally I just unplug the phone and plug it back in or close and reopen Eclipse but it is frustrating. Apparently Conversion to Dalvik format failed: Unable to execute dex: wrapper was not properly loaded first doesn't allow me to compile my app, i think it is because I was trying to run the emulator with some suggestions from emulator is so slow to no avail. thought i should add im running eclipse 3.5.2 on Ubuntu 11.04
Just restart the eclipse and run the project. The error arises while installing a new target version. After completion of the installation it will get fix automatically. Else restart eclipse.
I met with the same error on my Macbook. I tried one of the methods explained at this link http://techmologies.blogspot.com/2009/05/conversion-to-dalvik-format-failed-with_06.html and solved the problem.
Put the following 2 lines in the eclipse.ini file:
-vm
C:\Program Files\Java\jdk1.6.0_07\bin\javaw.exe
Please modify the 2nd line according to the actual situation.
If you have upgraded your SDK, and if you have not updated ADT plugin it will show this error. Please check it once by updating ADT plugin
I made a new installation of Eclipse in different folder(with the same SDK folder) and imported the code to the workspace & it started to work again.
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)
Some time ago my company migrated our Windows profiles and created new ones. I had an old installation of Eclipse Neon on the old profile.
I'm now trying to install a fresh copy of the latest eclipse and it always fails because it's trying to create folders for the old Windows profile, that doesn't exist.
Here's one of the errors it reports:
ERROR: org.eclipse.equinox.p2.artifact.repository code=1003 Unable to write to repository: file:/C:/Users/oldUser/.p2/pool.
java.io.IOException: Failed to create directory C:\Users\oldUser\.p2\pool\plugins.
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getOutputStream(SimpleArtifactRepository.java:1023)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:280)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:225)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:155)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:759)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
The folder C:\Users\oldUser does not exist anymore. Why isn't the installer installing it for the user I'm actually logged in as?
As far as I can tell, none of the old Eclipse Neon stuff still exists.
Turns out it had to do with a feature called "Bundle Pools". The installer, by default, has this feature turned on - it somehow knew / remembered the previous Neon installation and was trying to write to that. Turning off the "Bundle Pools" feature during the install allowed the setup to finish.