I have been using eclim for the past month and I was loving it.
Yesterday it all changed and now it doesn't work, the only things that changed on my machine are:
Sysadmin installed an encrypted partition not encroaching on any of the eclim or vim installation.
I Tried running another instance of eclipse on the same project from a different work space.
Eclim starts up, and performs basic functions, I can PingEclim etc.. but as soon as I try performing a save operation which is assumably exercising some java component it fails,
The output from starting eclim to the error is as follows:
java -jar "/home/user/dev/apps/eclipse/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -debug -clean -refresh -application org.eclim.application_headless
Install location:
file:/home/user/dev/apps/eclipse/
Configuration file:
file:/home/user/dev/apps/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/user/dev/apps/eclipse/configuration/
Framework located:
file:/home/user/dev/apps/eclipse/plugins/org.eclipse.osgi_3.6.2.R36x_v20110210.jar
Framework classpath:
file:/home/user/dev/apps/eclipse/plugins/org.eclipse.osgi_3.6.2.R36x_v20110210.jar
Debug options:
file:/home/user/dev/apps/eclipse/.options not found
Time to load bundles: 57
Starting application: 7989
2011-04-08 15:52:25,102 INFO [org.eclim.eclipse.AbstractEclimApplication] Workspace: /home/user/workspace
2011-04-08 15:52:25,103 INFO [org.eclim.eclipse.AbstractEclimApplication] Starting eclim...
Application Started: 9416
2011-04-08 15:52:26,132 INFO [org.eclim.eclipse.AbstractEclimApplication] Loading plugin org.eclim
2011-04-08 15:52:26,159 INFO [org.eclim.eclipse.AbstractEclimApplication] Loading plugin org.eclim.core
2011-04-08 15:52:26,467 INFO [org.eclim.plugin.core.CorePlugin] Loading eclim plugins...
2011-04-08 15:52:26,473 INFO [org.eclim.plugin.core.CorePlugin] Loading plugin org.eclim.maven
2011-04-08 15:52:26,475 INFO [org.eclim.plugin.core.CorePlugin] Loading plugin org.eclim.ant
2011-04-08 15:52:26,477 INFO [org.eclim.plugin.core.CorePlugin] Loading plugin org.eclim.jdt
2011-04-08 15:52:26,484 INFO [org.eclim.plugin.core.CorePlugin] Plugins loaded.
2011-04-08 15:52:26,485 INFO [org.eclim.eclipse.AbstractEclimApplication] Loaded plugin org.eclim.core
2011-04-08 15:52:26,489 INFO [org.eclim.eclipse.AbstractEclimApplication] Eclim Server Started on port 9091.
2011-04-08 15:52:26,580 WARN [org.eclim.plugin.jdt.PluginResources] Unable to locate jre src.zip for JAVA_HOME: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
NGSession 1: 127.0.0.1: org.eclim.command.Main exited with status 1
NGSession 2: 127.0.0.1: org.eclim.command.Main exited with status 1
NGSession 1: 127.0.0.1: org.eclim.command.Main exited with status 1
With the error part beign:
NGSession 1: 127.0.0.1: org.eclim.command.Main exited with status 1
NGSession 2: 127.0.0.1: org.eclim.command.Main exited with status 1
NGSession 1: 127.0.0.1: org.eclim.command.Main exited with status 1
I have tried re-installing eclim and have tried it on a differentnew version of eclipse.
If someone could give me a clue about what is going on or point me in the direction of how I might debug then it would help.
I had the exact same error, which was caused by the .project folder in my code folder. I got on track of this after reading this post. After deleting the .project folder, eclimd started up just fine.
When using emacs with eclim, the *Messages*-buffer can give you hints as to what could be wrong with the process, if the problem arises after eclimd has started. In vim it should be :Messages, although I'm not sure about this as I am no vim user.
Related
So yesterday I was installing extensions and then when opening my laptop today I wanted to explore some more and got a message saying that I had an error and check my logs and this is what [2018-06-07 10:51:07.049] [main] [info] update#setState idle
[2018-06-07 10:51:37.053] [main] [info] update#setState checking for updates
[2018-06-07 10:51:37.080] [main] [error] Error: net::ERR_INTERNET_DISCONNECTED
[2018-06-07 10:51:37.080] [main] [info] update#setState idle
How can I fix this ?
Okay I managed to fix it by doing the following command in my terminal (I'm using parrot security Os)
dpkg-reconfigure code
Eclipse Neon displays an error message box during startup and will not open. The message gives a file path to a log file. In that file I see this error message:
!ENTRY org.eclipse.e4.ui.workbench.swt 4 2 2016-11-13 08:50:49.856
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench.swt".
!STACK 0
java.lang.IllegalAccessError: com.aptana.editor.css.CSSSourceEditor.isWordWrapEnabled()Z
at org.eclipse.ui.texteditor.WordWrapToggleAction.isWordWrapEnabled(WordWrapToggleAction.java:66)
at org.eclipse.ui.texteditor.WordWrapToggleAction.update(WordWrapToggleAction.java:57)
at org.eclipse.ui.texteditor.TextEditorAction.<init>(TextEditorAction.java:68)
at org.eclipse.ui.texteditor.WordWrapToggleAction.<init>(WordWrapToggleAction.java:34)
at org.eclipse.ui.texteditor.AbstractTextEditor.createActions(AbstractTextEditor.java:5898)
at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createAction
The OS is Ubuntu 16.04
i found this solution and it worked for me.
I went to directory:
.metadata.plugins\org.eclipse.e4.workbench
And renamed
workbench.xmi to workbenchOLD.xmi
I found it here:
org.eclipse.swt.SWTException: “Widget is disposed” when trying to open AndroidManifest.xml
I hope it helped!
See you,
Federico
When using the Eclipse Jetty plugin (http://marketplace.eclipse.org/content/eclipse-jetty?mpc=true&mpc_state=), I started to get the following error:
An internal error occurred during: "Launching myProject".
Unknown scope: test,provided
This started to occur for two separate projects, both on Windows and MacOs X systems. Note that a regular Jetty deployment, as well as the Jetty runner Maven plugin, work like a charm, the problem seems to be with the Eclipse plugin only. The problem persists after upgrading the plugin to the newest version. Changing Jetty versions doesn't help as well.
edit: Thanks for the tips so far. The question is what might be the source of this problem and how to get rid of it. The relevant log message is as follows:
!ENTRY org.eclipse.core.jobs 4 2 2016-04-27 09:01:40.914
!MESSAGE An internal error occurred during: "Launching myProject".
!STACK 0
java.lang.IllegalArgumentException: Unknown scope: test,provided
at net.sourceforge.eclipsejetty.util.MavenScope.to(MavenScope.java:109)
at net.sourceforge.eclipsejetty.util.MavenDependencyInfo.create(MavenDependencyInfo.java:98)
at net.sourceforge.eclipsejetty.util.MavenDependencyInfoMap.resolve(MavenDependencyInfoMap.java:141)
at net.sourceforge.eclipsejetty.util.Dependency.create(Dependency.java:39)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.getOriginalClasspathEntries(JettyLaunchConfigurationDelegate.java:340)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.createJettyConfigurationFile(JettyLaunchConfigurationDelegate.java:791)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.getVMArguments(JettyLaunchConfigurationDelegate.java:217)
at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:64)
at net.sourceforge.eclipsejetty.launch.util.JettyLaunchConfigurationDelegate.launch(JettyLaunchConfigurationDelegate.java:192)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Try running Eclipse with a console and debug info to see if more error details are available: add -console, -consoleLog and -debug to your eclipse.ini to achieve this.
Try using the Run Jetty Run plugin instead of the Maven Jetty plugin
I just installed Klocwork plugin for Eclipse. But when I start to scan a project, it gives me the following error:
java.lang.UnsatisfiedLinkError: no sqlite_jni in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.klocwork.desktopdb.SqliteJniLoader.initDefaultLibraries(SqliteJniLoader.java:28)
at com.klocwork.desktopdb.SqliteAgent.<clinit>(SqliteAgent.java:21)
at com.klocwork.desktopdb.migration.MigrateDesktopDb.<init>(MigrateDesktopDb.java:48)
at com.klocwork.desktopdb.migration.MigrateDesktopDb.migrate(MigrateDesktopDb.java:44)
at com.klocwork.desktopdb.KwlpProblemsStorageUtil.migrateOrCreateStorage(KwlpProblemsStorageUtil.java:32)
at com.klocwork.kwcheck.commands.AbstractCommand.convertToDB(AbstractCommand.java:82)
at com.klocwork.kwcheck.commands.BuildCommand.execute(BuildCommand.java:110)
at com.klocwork.util.CommandLineParser2.parse(CommandLineParser2.java:360)
at com.klocwork.kwcheck.KwCheckMain.main(KwCheckMain.java:22)
kwcheck: WARNING: Exception occured in java application
Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true -Djava.library.path=".;C:\Program Files (x86)\myLib\win32"
Exception in thread "main"
I found several threads with similar issues:
http://thelogofthewook.blogspot.de/2011/12/updating-problems-myproject-no.html
https://developer.klocwork.com/community/forums/klocwork-general/user-tools/eclipse-plugin-error
They all mentioned some 32bit/64bit issue. But I am using 32bit Eclipse + 32bit JVM.
And as I checked, there are 2 different sqlite_jni.dll files existing in the plugin's lib and lib64 folders respectively. So I guess no file is missing.
So what could be wrong?
Currently, I am trying to troubleshoot it in the following ways:
Figure out how a plugin locates its native libraries.
How to configure java.library.path for a plugin.
A little patience pays off...
I read carefully the error message and it clearly says:
Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
-Djava.library.path=".;C:\Program Files (x86)\myLib\win32"
So I suddenly recall that I once set a environmental variable like this:
_JAVA_OPTIONS = -Djava.net.preferIPv4Stack=true -Djava.library.path=".;C:\Program Files (x86)\myLib\win32"
After I changed it to below, things begin to work.
_JAVA_OPTIONS = -Djava.net.preferIPv4Stack=true
And some background reference:
http://examples.javacodegeeks.com/java-basics/java-library-path-what-is-it-and-how-to-use/
I'm trying to run a headless eclipse build but I'm getting stuck. My context is that I want to use the PyDev code analysis without having to fire up the eclipse gui. I am aware of the other command line tools to do code analysis (pyflakes, pylint, etc).
The command I have so far is:
java -jar /path/to/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -noSplash -data "/path/to/workspace" -application org.eclipse.jdt.apt.core.aptBuild
My java version 1.6.0_31, my eclipse version is 3.7.2, and my pydev version is 2.5.0.
When I run the command, it looks like it is working, but it never catches any errors or warnings.
...
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
PyDev: Analyzing 29 of 33 (forms.py)
...
If I tail -f /path/to/workspace/.metadata/.log, I get a huge stack trace:
!ENTRY org.eclipse.equinox.preferences 4 2 2012-07-30 17:48:39.612
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.ExceptionInInitializerError
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.setDefault(DebugUIPreferenceInitializer.java:186)
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.setThemeBasedPreferences(DebugUIPreferenceInitializer.java:204)
at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.initializeDefaultPreferences(DebugUIPreferenceInitializer.java:79)
at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper$1.run(PreferenceServiceRegistryHelper.java:281)
..... TRUNCATED ......
!ENTRY org.eclipse.osgi 4 0 2012-07-30 17:48:39.622
!MESSAGE An error occurred while automatically activating bundle org.eclipse.debug.ui (42).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.debug.internal.ui.DebugUIPlugin.start() of bundle org.eclipse.debug.ui.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
..... TRUNCATED .......
java.lang.IllegalStateException: Workbench has not been created yet.
at org.eclipse.ui.PlatformUI.getWorkbench(PlatformUI.java:92)
at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.startup(LaunchingResourceManager.java:546)
at org.eclipse.debug.internal.ui.DebugUIPlugin.getLaunchingResourceManager(DebugUIPlugin.java:315)
at org.eclipse.debug.internal.ui.DebugUIPlugin.start(DebugUIPlugin.java:516)
..... TRUNCATED ......
!ENTRY org.eclipse.osgi 4 0 2012-07-30 17:48:39.624
!MESSAGE An error occurred while automatically activating bundle org.eclipse.debug.core (41).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.debug.core.DebugPlugin.start() of bundle org.eclipse.debug.core.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
..... TRUNCATED ......
My suspicion is that PyDev needs the gui to render the errors/warnings.
PyDev needs the gui to render errors/warnings and in general it was not done to be used in the command line... now, having said that, it does have unit-tests that run the code-analysis without requiring a gui (nor even eclipse loaded), but you have to configure the interpreter/projects in-memory for that to work.
See:
https://github.com/aptana/Pydev/blob/development/plugins/com.python.pydev.analysis/tests/com/python/pydev/analysis/OccurrencesAnalyzerTest.java
https://github.com/aptana/Pydev/blob/development/plugins/com.python.pydev.analysis/tests/com/python/pydev/analysis/AnalysisTestsBase.java
for tests that do code-analysis without requiring the eclipse workbench to be loaded at all (i.e.: doesn't even need eclipse to be run headless -- it could be run as a simple java program, but you still have to do the java main([]) using PyDev in the CLASSPATH and using its API to properly set the interpreter used in PyDev as well as the projects/pythonpath).
You can take a look at the setUp of the tests (i.e.: don't forget to also look superclasses such as CodeCompletionTestsBase/AnalysisTestsBase).
Note: if you do create such a main([]), please provide a patch for PyDev as it may be used by others...
As an implementation note, such a main should probably gather all the current PYTHONPATH entries from the shell being launched and configure all of those in the interpreter... Also, it should probably receive a directory as a parameter so that it analyzes all files in the tree (the startup is probably going to take the most of your time to configure things, so, ideally analyze as much files as you can from a single run, as the PyDev code-analysis was done to cache lots of things in the startup and then use the information from RAM -- or maybe create a server process that's always live?).