When I try to uninstall my eclipse plugin the following error occurs:
An error occurred while uninstalling
enter code heresession context was:(profile=profile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Uninstall, operand=[R]de.test.package.one 0.1.0.201008170949 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
Error while loading manipulator.
Caused by: Application failed,
Most topics refer to the eclipse.ini file, which I modified but that didn't solve the problem. The eclipse.ini looks like this:
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520
Any ideas how I can solve this problem?
I would like you to know that I solved the: "An error occurred while uninstalling" problem. by:
1.) rename the eclipse.ini file to a non ini name (eclipse.xxx)
2.) start eclipse
3.) Install the software/plugin
4.) restore the ini file.
I wonder why Eclipse can start in the first place but it works.
The renaming of the executable did NOT work for me.
Related
Whenever I try to edit an xhtml file in eclipse, it shows an internal error:
An internal error occured during "Processing variables for ...xhtml"
Could not initialize class org.apache.myfaces.shared.config.MyfacesConfig
Is there a way to fix this problem?
Stack trace:
java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.shared.config.MyfacesConfig
at oracle.eclipse.tools.webtier.jsf.facelet.DTFacesConfigurator.configureApplication(DTFacesConfigurator.java:683)
at oracle.eclipse.tools.webtier.jsf.facelet.DTFacesConfigurator.configure(DTFacesConfigurator.java:414)
at oracle.eclipse.tools.webtier.jsf.facelet.FaceletCompilerConfigurator.configure(FaceletCompilerConfigurator.java:118)
at oracle.eclipse.tools.webtier.jsf.facelet.FaceletCompilerConfigurator.configure(FaceletCompilerConfigurator.java:97)
at oracle.eclipse.tools.webtier.jsf.facelets.OepeFaceletCompiler.createConfig(OepeFaceletCompiler.java:113)
at oracle.eclipse.tools.webtier.jsf.facelets.OepeFaceletCompiler.compile(OepeFaceletCompiler.java:78)
at oracle.eclipse.tools.webtier.jsf.facelets.FaceletCompileUtil.ensureContext(FaceletCompileUtil.java:35)
at oracle.eclipse.tools.webtier.jsf.dependency.discovery.FaceletDiscoveryParticipant.discover(FaceletDiscoveryParticipant.java:267)
at oracle.eclipse.tools.webtier.jsf.dependency.discovery.FaceletDiscoveryParticipant.discoverFromExistingModel(FaceletDiscoveryParticipant.java:361)
at oracle.eclipse.tools.application.common.services.variables.VariablesController$DocumentRediscoveryJob.runAfterCommands(VariablesController.java:746)
at oracle.eclipse.tools.common.services.concurrency.AbstractJob.run(AbstractJob.java:73)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
All x-friends directives in the manifest file referenced to a wrong bundle.
Fix for the most recent version of OEPE (12.1.3.3.1):
Replace META-INF\MANIFEST.MF in plugins\oracle.eclipse.tools.webtier.jsf.facelet_7.3.3.201412231459.jar with this.
Restart eclipse
I met an error when I exported the Eclipse Product using the export wizard on the overview tab of the .product file ,
the error message is as below .
but it worked just fine when I ran it from inside of Eclipse as an Eclipse Application.
can anybody provide some idea about this .
C:\workSpace\0709\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:90: The following error occurred while executing this line:
C:\workSpace\0709\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86_64.xml:1140: The following error occurred while executing this line:
C:\tool\eclipse-standard-kepler-SR2-win32-x86_64\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\genericTargets.xml:243: A problem occured while invoking the director.
Thanks & Regards,
Jeff
The originating problem is somewhere else.. To find it out add following line to your genericTargets.xml under node <target name="runDirector"> -> <record name="path_to_log_output_file" loglevel="verbose"> . Then you will probably see actual problem.
I got a very strange error. This what I've done:
I create a project (with Netbeans) which include datanucleuse-core-3.0.0-release.jar. The project can be built successfully. It also ran smoothly when I tried to run it with Netbeans or running 'java -jar <.jar bundle>' in dist folder via command prompt.
The problem is, when I copy that dist folder into another location and tried to run it again with command prompt, it gave these errors:
Exception in thread "main" Error reading manifest file
"jar:file:/E:/!new/BTJ/NCRServer/lib/datanucleus-core-3.0.0-release.jar!/plugin.xml"
org.datanucleus.exceptions.NucleusException: Error reading manifest
file "jar:fi
le:/E:/!new/BTJ/NCRServer/lib/datanucleus-core-3.0.0-release.jar!/plugin.xml"
at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle(NonMan
agedPluginRegistry.java:481)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensions(No
nManagedPluginRegistry.java:219)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensionPoin
ts(NonManagedPluginRegistry.java:160)
at org.datanucleus.plugin.PluginManager.(PluginManager.java:62)
at org.datanucleus.NucleusContext.(NucleusContext.java:211)
at org.datanucleus.NucleusContext.(NucleusContext.java:166)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.(JDOPersis
tenceManagerFactory.java:360)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenc
eManagerFactory(JDOPersistenceManagerFactory.java:290)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceMa
nagerFactory(JDOPersistenceManagerFactory.java:191)
at com.ncr.server.Server.(Server.java:68)
at com.ncr.server.Server.main(Server.java:91) Caused by: java.io.FileNotFoundException: E:\ (The system cannot find the path s
pecified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:114)
at java.util.jar.JarFile.(JarFile.java:135)
at java.util.jar.JarFile.(JarFile.java:99)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle(NonMan
agedPluginRegistry.java:390)
... 10 more Nested Throwables StackTrace: java.io.FileNotFoundException: E:\ (The system cannot find the path
specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:114)
at java.util.jar.JarFile.(JarFile.java:135)
at java.util.jar.JarFile.(JarFile.java:99)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerBundle(NonMan
agedPluginRegistry.java:390)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensions(No
nManagedPluginRegistry.java:219)
at org.datanucleus.plugin.NonManagedPluginRegistry.registerExtensionPoin
ts(NonManagedPluginRegistry.java:160)
at org.datanucleus.plugin.PluginManager.(PluginManager.java:62)
at org.datanucleus.NucleusContext.(NucleusContext.java:211)
at org.datanucleus.NucleusContext.(NucleusContext.java:166)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.(JDOPersis
tenceManagerFactory.java:360)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.createPersistenc
eManagerFactory(JDOPersistenceManagerFactory.java:290)
at org.datanucleus.api.jdo.JDOPersistenceManagerFactory.getPersistenceMa
nagerFactory(JDOPersistenceManagerFactory.java:191)
at com.ncr.server.Server.(Server.java:68)
at com.ncr.server.Server.main(Server.java:91)
Anybody got clue ?
I am really sorry for everyone, especially for datanucleus members in StackOverflow.
Apparently the problem is me, not the netbeans, datanucleus API, nor anyone.
As you can see from "jar:file:/E:/!new/BTJ/NCRServer/lib/datanucleus-core-3.0.0-release.jar!/plugin.xml", I put the "dist" folder from Netbeans in "E:/!new" folder. I don't know why but the "!new" folder seems to cause the extra exclamation mark(!) in "release.jar!".
I move the dist folder into D:/ and it worked !!
So, if anyone ever experience this problem (precedence a folder's name with exclamation mark and accidentally put a project with datanucleus-core-3.0.0-release.jar inside it), that's the solution.
Thank you.
I get the following error when trying to start ENSIME on OSX through Emacs
Error running ensime-source-buffer-loaded-hook
I am following the instructions from the github source page
Scala Mode is Working
ENSIME Server appears to be installed, is there any way to verify this?
The sbt plugin is installed and I have a .ensime config file generated
Starting Emacs gives me the above error. When I manually try M-x ensime I get the following:
Failed to connect to Swank: server process exited.
Okay, here's how I solved it:
Locate the ensime folder and run bin/server /tmp/ensime.port.
I got the error:
java -classpath ... org.ensime.server.Server ./port
Unrecognized VM option '+DoEscapeAnalysis'
Could not create the Java virtual machine.
I have no idea what DoEscapeAnalysis is for, but I tried deleting it from bin/server and now everything seems to work.
See here: https://gist.github.com/2300737
For my case on Windows 7, with the same error message, but the root cause was the original setting for the maximum heap size -Xmx1512M was too large, I had to change to -Xmx768M to get over the error message.
I had also removed the byte compiled elisp code, and restart to avoid another error of
"call time out".
I also had this error on linux with emacs 24.3.1 and resolved it by specifying the full path to java in bin/server.
I'm continually getting the following error under Eclipse Galileo while trying to install the WTP Web Page Editor plugin:
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:54)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:76)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:29)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
One blog said Eclipse Galileo doesn't play well with Java 1.6 (what??), so I've tried running Eclipse with Java 1.5 but that hasn't helped. Has anyone else had this problem and been able to get around it?
Edit BTW, below the error in the error log it also says
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Install, operand=null --> [R]javax.mail 1.4.0.v200905040518, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
You can try to follow the various suggestions mentioned in the bug 277242
Also check your eclipse.ini:
More generally, the error you're seeing can happen when we cannot read "-startup" since we use this to position the install.area.
As suggested by Jelle van Geuns in the comments (and confirmed by Halfstop):
I found that one MacOS there are two folders (MacOS and Eclipse) with two separate sets of configuration files.
Each had an 'org.eclipse.equinox.launcher' startup jar in the plugins sub-folder, but with slightly different versions.
The Eclipse executable resides in the MacOS folder.
But the eclipse.ini there was set up to look for the startup jar under Eclipse/plugins, but with the wrong version.
Solution that worked for me was to copy both versions of the startup.jar to both the plugins sub-folders.
Halfstop confirms:
I copied all of the what was in Eclipse to the MacOS directory and this solved it.
I just ran into this problem today. The answer provided by VonC et al helped to locate the problem but didn't quite fix it.
In my case, the location specified in -startup within the MacOS/eclipse.ini was incorrectly looking in the ../Eclipse/plugins folder rather than the ../MacOS/plugins folder.
I corrected the path and the error went away.
try to chown -R your_user_name:your_user_name /path/to/eclipe
Try edit
Eclipse/configuration/config.ini.
Make sure osgi.instance.area.default= value is right workspace. This works for me.
I'm not sure if the above answers adequately resolve this issue. I've found that, with a number of our eclipse derivative RCP products, that on some linux machines plugins will fail with log entries like this one:
!ENTRY org.eclipse.equinox.p2.engine 4 4 2017-02-23 12:00:49.492
!MESSAGE An error occurred while installing the items
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492
!MESSAGE session context was:(profile=TIBCOBusinessStudio-4.0, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.tibco.eclipse.p2.installer 1.1.3.20161130, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:59)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:75)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:32)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:38)
at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:183)
at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:95)
at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:47)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:159)
at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
The reason this happens (I suspect) is that the actual file name of the config file is compared with the absolute name by the lazyloader. In my case the home dir is a symlink, so the two names don't match. The resolution was to edit the eclipse.ini (or whatever yours is called) and ensure that all the paths referencing the eclipse home dir are fully qualified and do not rely on symlinks.