I'm trying to install groovy plugin in eclipse 3.5 using this update site.
It does install but when it tries to restart I get an exception.
!SESSION Sat Aug 29 15:47:17 PDT 2009 ------------------------------------------
!ENTRY org.eclipse.equinox.launcher 4 0 2009-08-29 15:47:17.287
!MESSAGE Exception launching the Eclipse Platform:
!STACK java.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
I tried to start using -clean options,deleted workspace no luck
Did anyone get this too??
It looks like you're missing a class or a jar required by the plugin; I'm not sure which one though, since the stacktrace does not indicate any such plugin specific class. You could attempt the following:
Examine the .log file of the workspace to view any additional details of the exception.
Verify if all the Groovy Eclipse plugin jars are present in the plugins and features directory of the Eclipse installation.
Start Eclipse with the consolelog and debug switches, and pipe the output to a debug log file. Examine for anything indicative of the problem in the logfile; if needed post the log file. The command to start Eclipse in this mode would be $eclipse -consolelog -debug | tee debugfile.log
Install the plugin on a clean installation of Eclipse.
OK now finally i fixed it after 2 days of war with eclipse, so for some reason when groovy plugin was installed eclipse modified config.ini file inside configuration folder
so I have to modify config.ini file to replace osgi.bundles value with
osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.100.v20090520-1905.jar#1\:start,reference\:file\:plugins/org.eclipse.jdt.core_3.5.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.apache.commons.collections_3.2.1.jar#4,reference\:file\:/Applications/galileo/plugins/org.apache.commons.lang_2.3.0.v200803061910.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy_1.7.0.xx-20090828-1900-e35/#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.ant_2.0.0.xx-20090828-1900-e35/#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.codeassist.completion_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.codebrowsing_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.core_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.core.help_2.0.0.xx-20090828-1900-e35/#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.cstviewer_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.refactoring_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.codehaus.groovy.eclipse.ui_2.0.0.xx-20090828-1900-e35.jar#4,reference\:file\:/Applications/galileo/plugins/org.eclipse.jdt.groovy.core_1.0.0.xx-20090828-1900-e35.jar#4
By default osgi.bundles value is osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.100.v20090520-1905.jar#1\:start but as soon as I installed groovy plugin I had a modified value which caused eclipse fali to start.
now my eclipse starts and i see the groovy features too..
I had the same problem with installing the CVS plugin on a Eclipse Platform installation running TeXlipse. Turns out, after installing CVS, the installer had modified not the osgi.bundles, but the osgi.framework.
/Applications/TeXlipse/configuration/config.ini said:
osgi.framework=file\:/Applications/TeXlipse/Eclipse.app/Contents/MacOS/plugins/org.eclipse.osgi_3.5.2.R35x_v20100126.jar
and it was supposed to say
osgi.framework=file\:/Applications/TeXlipse/plugins/org.eclipse.osgi_3.5.2.R35x_v20100126.jar
Related
After starting Eclipe I see the following error message in the workspace/.metadata/.log
!ENTRY org.eclipse.core.runtime 4 0 2017-09-18 09:38:48.275
!MESSAGE Invalid input url:platform:/plugin/com.mountainminds.eclemma.ui/icons/full/eview16/coverage.gif
!STACK 0
java.io.IOException: Unable to resolve plug-in "platform:/plugin/com.mountainminds.eclemma.ui/icons/full/eview16/coverage.gif".
The message does not go away even after uninstalling or reinstalling the plugin.
Any ideas on how to resolve this?
Eclipse: Oxygen 4.7.0
EclEmma: 3.0.0
EclEmma became an Eclipse project and is now part of the Eclipse Java download packages. Due to the move, the plug-ins have been rename: com.mountainminds.eclemma.ui become org.eclipse.eclemma.ui.
If you use a workspace that have been used with EclEmma < 3.0.0 before,
start Eclipse with the option -clean and
reset all Java perspectives (coverage.gif is the icon of the Coverage view and could be referenced in the stored window/perspective layout).
This is the image the error is referring to.
Put it in the proper installation path on your machine and you'd be fine.
I am having trouble configurating Eclipse for MD 18.3 plugin development.
I have thoroughly followed the "MagicDraw 18.3 Developer Guide / Development in Eclipse" tutorial you can find inside MagicDraw\openapi section to set up Eclipse.
When launching MagicDraw with all plugins run configuration, it throws the following error and terminates:
!ENTRY org.eclipse.core.variables 4 120 2016-07-20 10:39:12.159
!MESSAGE Reference to undefined variable file_uri
caused by this line of the run configuration
-Dosgi.framework.extensions=reference:${file_uri:${workspace_loc:/MagicDraw/MAGIC_DRAW_INSTALL_DIRECTORY/lib/bundles}}/com.nomagic.magicdraw.osgi.fragment
However, \lib\bundles\com.nomagic.magicdraw.osgi.fragment_1.0.0.201601271815.jar
is existing
I'm running the demo license, but that shouldn't influence the configuration. Any suggestions?
UPDATE
Solved this issue, by replacing reference:${file_uri:${workspace_loc:/MagicDraw/MAGIC_DRAW_INSTALL_DIRECTORY/lib/bundles}}/com.nomagic.magicdraw.osgi.fragment with the actual path and enabling com.nomagic.magicdraw.platform.feature in the bundles tab of the run configuration.
Next Problem: The provided example plugins won't load, throwing
java.lang.NullPointerException at com.nomagic.magicdraw.plugins.XMLPluginDescriptorLoader.loadPluginDescriptorData(XMLPluginDescriptorLoader.java:172)
and therefore
ERROR PLUGINS - Failed to create plugin: My Plug-in 2
java.lang.ClassNotFoundException: myplugin2.MyPlugin2
Same message for both, the example plugins and my own plugin. I have checked the plugin.xml files and also experimentally enabled the run configurations > bundles > workspace checkbox.
Try to edit this line:
- Dosgi.framework.extensions=com.nomagic.magicdraw.osgi.fragment
Setting up a new clean Eclipse installation solved everything.
I updated the Eclipse SVN plugins today and after that I can't sync my workspace with SVN repository.
I am using java 1.6. I tried with java 1.7 as well. still I'm getting following error in eclipse.
An internal error occurred during: "Updating Synchronize view for SVN Workspace.".
java/nio/file/Paths.
SVN: '0x00000025: Send Notifications' operation finished with error:
java/nio/file/Paths
This issue came only after updating the svn plugin. I'm using SVNKit 1.7.13 svn connector.
Any idea how to solve this??
Thanks
Found a work around for this.
Uninstalled all svn plugins from Eclipse and restarted it.
Installed Subclipse svn plugin from http://subclipse.tigris.org/update_1.10.x
I had the same error when I opened Eclipse. Checking the file: workspase-path/.metadata/.log I found the following exception:
!MESSAGE SVN: 'SVN Decorator' operation finished with error: java/nio/file/Paths
!STACK 0
java.lang.NoClassDefFoundError: java/nio/file/Paths
at org.eclipse.team.svn.core.utility.SVNUtility.getNodeKind(SVNUtility.java:1145)
...
To solve the problem I installed JRE 1.7, then I changed eclipse.ini to force Eclipse to use it, adding the next at the beginning:
-jv
"path-to-jre7/bin/javaw.exe"
I had the same problem in Luna on Win 7 64 bit with the 2.0.3 subversive team provider and the Polarion SVNKit 1.8.7 version 4.1.2. Clearly somewhere in these java 7 is needed. Servaq's suggestion improved things for me but didn't quite fix everything. But a similar change to eclipse.ini did the trick for me: I added
-vm
C:\Program Files\Java\jre7\bin\server\jvm.dll
right before the -vmargs. Obviously, the path to server\jvm.dll is installation-dependent.
Just in case it's helpful to Chandika ("I wants to use java 1.6"),
I'm still using java 6 as the compiler/runtime for the code I'm developing within this eclipse. I'm just using java 7 to start eclipse.
Plugin A uses a class,ClassB, which is from Plugin B.When "run as eclipse application", everything goes well; however, when PluginA adn Plugin B are exported as Jar, and install into a new eclipse platform, they run well independently, but crash when the codes reach the line where Plugin A uses the ClassB.
error log: ava.lang.NoClassDefFoundError Caused by: java.lang.ClassNotFoundException
In plugin org.jboss.vpe.browsersim.eclipse, there is BrowserSimLauncher.java in the package org.jboss.vep.browsersim.eclipse.launcher;
In plugin org.ayound.js.debug.core, there exits a java file "JsLaunchConfigurationDelegate.java", and I put BrowserSimLauncher.launchBrowserSim(startUrl);
into it, this means I've used previous plugin's class 'BrowserSimLauncher' in the latter plugin.
I also do all the"dependencies things", including adding lines to latter plugin's manifest.mf:
Import-Package: org.jboss.tools.vpe.browsersim.eclipse.launcher
and to previous plugin's manifest.mf:
Export-Package: org.jboss.tools.vpe.browsersim.eclipse.launcher
In the development environment, both plugins compiles successfully, when "run as eclipse application", things goes well, and the latter plugin can sucessfully call BrowserSimLauncher.launchBrowserSim(startUrl); ;
however, when I exported both plugins as several .jar files, and copy them into the /plugin folder of another eclipse directory, start the eclipse, both plugins can run well independently, but the plugin fails to call BrowserSimLauncher.launchBrowserSim(startUrl);. and the error log show as follow:
!ENTRY org.eclipse.core.jobs 4 2 2015-01-06 16:29:03.817
!MESSAGE An internal error occurred during: "Launching index.html".
!STACK 0
java.lang.NoClassDefFoundError: org/jboss/tools/vpe/browsersim/eclipse/launcher/BrowserSimLauncher
at org.ayound.js.debug.launch.JsLaunchConfigurationDelegate.launch(JsLaunchConfigurationDelegate.java:101)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.ClassNotFoundException: org.jboss.tools.vpe.browsersim.eclipse.launcher.BrowserSimLauncher cannot be found by org.ayound.js.debug.core_2.2.0
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 6 more
the latter plugin(js.debug.core) can't find the previous plugin(browsersim.eclipse)!
If you just copy plugins in to the Eclipse 'plugins' directory then you need to specify the '-clean' option when you start Eclipse to get it to rebuild the plugin dependencies cache.
You can specify '-clean' on the Eclipse command line or in the eclipse.ini file (here it must be before any -vmargs line).
It is safe to always specify -clean but it will slow down the Eclipse start a bit.
supplements:
Just startup eclipse with option "-clean", problem solved. Details are from reference article:
What it does:
if set to "true", any cached data used
by the OSGi framework and eclipse
runtime will be wiped clean. This will
clean the caches used to store bundle
dependency resolution and eclipse
extension registry data. Using this
option will force eclipse to
reinitialize these caches.
How to use it:
Edit the eclipse.ini file located in your Eclipse install directory and insert -clean as the first line.
Or edit the shortcut you use to start Eclipse and add -clean as the first argument.
Or create a batch or shell script that calls the Eclipse executable with the -clean argument. The advantage to this step is you can keep the script around and use it each time you want to clean out the workspace. You can name it something like eclipse-clean.bat (or eclipse-clean.sh).
(From: http://www.eclipsezone.com/eclipse/forums/t61566.html)
Other eclipse command line options: http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html
I've recently done a fresh install of Ubuntu 11.10, installing the latest version of Eclipse CDT. I'm trying to debug an existing C++ project with makefiles and Eclipse project files generated by CMake. Upon attempting to debug (with all of the correct settings given in the Debug Configuration), the launch fails with error:
An internal error occurred during: "Launching mops-app".
java.lang.NullPointerException
This does not occur when trying to debug a minimal Hello World project. The project could be successfully debugged on Ubuntu 11.04 with the latest version of Eclipse CDT. The java version on my machine is:
java version "1.6.0_23"
OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre10-0ubuntu5)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
And the Eclipse output from trying to launch the debug configuration is:
!ENTRY org.eclipse.core.jobs 4 2 2011-10-31 11:50:24.211
!MESSAGE An internal error occurred during: "Launching mops-app".
!STACK 0
java.lang.NullPointerException
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1837)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1848)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1848)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setSourceLookupPath(CDebugTarget.java:1815)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initializeSourceLookupPath(CDebugTarget.java:383)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initialize(CDebugTarget.java:282)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init>(CDebugTarget.java:275)
at org.eclipse.cdt.debug.core.CDIDebugModel$1.run(CDIDebugModel.java:100)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)
at org.eclipse.cdt.debug.core.CDIDebugModel.newDebugTarget(CDIDebugModel.java:105)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSession(LocalCDILaunchDelegate.java:162)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(LocalCDILaunchDelegate.java:112)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaunchDelegate.java:72)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
The issue was associated with upgrading the version of CMake. CMake 2.8.5 generated 'Subproject' entries in the Eclipse .cproject and .project files. For some reason, CMake by default told Eclipse to ignore the Subproject paths, thus confusing Eclipse's indexer when it tried to debug code.
The problem is easily resolved by commenting-out the <linkedResources> entry of the .project file, e.g.
<!--link>
<name>[Subprojects]/MOPS</name>
<type>2</type>
<location>/home/user/mops-c-Git/src/mopsc</location>
</link-->
and commenting-out the Subproject portion <pathentry> entry of the .cproject file, e.g.
<!--pathentry kind="src" path="MOPS"/>
<pathentry excluding="MOPS/|**/CMakeFiles/" kind="out" path=""/-->
Make sure to have selected the executable to run in the Run/Run or Run/Debug menu.
I had a similar problem (Ubuntu 14.04, SBT 13.1.0) - launching Debugger caused a java.lang.NullPointerException. Checking the log by starting Eclipse with eclipse-nios2 -consoleLog, I had similar entries:
java.lang.NullPointerException
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1843)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1864)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.getSourceLookupPath(CDebugTarget.java:1864)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setSourceLookupPath(CDebugTarget.java:1817)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initializeSourceLookupPath(CDebugTarget.java:385)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initialize(CDebugTarget.java:286)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init>(CDebugTarget.java:279)
I believe the cause is the same; I found another fix and wanted to share it for completeness.
I have linked resources in my project, and the log made me suspect they were the cause. I had linked the resources with Import->General->File system->[... Create links in workspace...].
I removed these links and instead linked to the sources by Project Properties->C/C++ General->Paths and Symbols->[tab] Source Location->Link folder....
This made the Debugger run fine without complaining.