How Do You Upgrade From Eclipse Ganymede to Eclipse Galileo? - eclipse-rcp

I have written an RCP application that contains numerous plugin-ins I have created using Ganymede version 3.4.2. I want to start using Galileo. When I try to execute my RCP application from the Workspace I created using Ganymede I get lots of errors like the following:
!SESSION 2009-09-09 10:41:33.907 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product com.bah.gs.arts.jekyll.product
Command-line arguments: -product com.bah.gs.arts.jekyll.product -data C:\Workspace/../runtime-jekyll.product -dev file:C:/Workspace/.metadata/.plugins/org.eclipse.pde.core/jekyll.product/dev.properties -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.equinox.app 0 0 2009-09-09 10:41:35.469
!MESSAGE Product com.bah.gs.arts.jekyll.product could not be found.
!ENTRY org.eclipse.osgi 2 0 2009-09-09 10:41:35.500
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 10:41:35.500
!MESSAGE Bundle initial#reference:file:../../Common/plugins/org.eclipse.core.databinding_1.2.0.I20090604-2000.jar/ was not resolved.
!SUBENTRY 2 org.eclipse.core.databinding 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.observable_[1.2.0,2.0.0).
!SUBENTRY 2 org.eclipse.core.databinding 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.property_[1.2.0,2.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 10:41:35.500
!MESSAGE Bundle initial#reference:file:../../Common/plugins/org.eclipse.jface.databinding_1.3.0.I20090525-2000.jar/ was not resolved.
!SUBENTRY 2 org.eclipse.jface.databinding 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.property_[1.2.0,2.0.0).
!SUBENTRY 2 org.eclipse.jface.databinding 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.observable_[1.2.0,2.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 10:41:35.500
!MESSAGE Bundle initial#reference:file:../../Common/plugins/org.eclipse.ui.workbench_3.5.0.I20090603-2000.jar/ was not resolved.
!SUBENTRY 2 org.eclipse.ui.workbench 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.property_[1.2.0,2.0.0).
!SUBENTRY 2 org.eclipse.ui.workbench 2 0 2009-09-09 10:41:35.500
!MESSAGE Missing required bundle org.eclipse.core.databinding.observable_[1.2.0,2.0.0).
Why is upgrading from one Eclipse version to the next so painful?
Is there a systematic way of resolving the above issues?
Is there a "best practices" upgrade procedure available?
Thanks for your help.
After trying what VonC suggested I am still experiencing some problems.
This is the constraint part of the MANIFEST.MF for the RCP application:
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Require-Bundle: org.eclipse.core.runtime;bundle-version="3.5.0";resolution:=optional;visibility:=reexport,
org.eclipse.ui;bundle-version="3.5.0";resolution:=optional;visibility:=reexport,
org.eclipse.core.expressions;bundle-version="3.4.100";resolution:=optional;visibility:=reexport
What is the significance of the "visibility:=reexport" and "resolution:=optional" parameters?
Error messages:
org.eclipse.core.databinding
Missing Constraint:Required-Bundle: org.elclipse.core.databinding.observable;require-version="[1.2.0.2.0.0]"
Missing Constraint:Required-Bundle: org.elclipse.core.databinding.property;require-version="[1.2.0.2.0.0]"
Same two messages for:
org.eclipse.jface.databinding
org.eclipse.ui.workbench

The error you listed says that Galileo doesn't see all the plug-ins and libraries Ganymede and your program was using. Sorry for the non-answer below. Your alternative is fiddling with Galileo until it sees all your libraries and plug-ins.
What I would do is install Galileo side-by-side Ganymede and port your applications over one at a time. I'm assuming you are working under Windows, but the same techniques that I list here also work for Linux.
First, in theory, all you have to do to upgrade from Ganymede to Galileo is install Galileo over Ganymede. Believe that? Good. I don't either. So walk through Ganymede and note what plug-ins you have installed. Then install Galileo in a separate directory. Point the new install at your Java VM. Then install all your plug-ins. It's your choice how you do this.
Finally, I'd differentiate between source and Meta in your projects. Create a new project under Galileo and move only your source. Let Galileo re-build your meta.
Now, how to avoid all this pain next time: Version control. CVS, SVN, git... it doesn't matter what you use. Eclipse has a plug-in that supports them all. Then, next upgrade, simply import the source into a project in your new Eclipse installation. Much less painful, and you'll have much more control over your source.
Good luck.

I am using eclipse for developing code in Java, Python and PHP. I was using Ganymede to do all this, until I wanted to upgrade to Galileo. The upgrade was quite simple. These are the steps I followed:
Back up the workspace somewhere where uninstalling Ganymede won't affect it.
Copy all the software sites onto a text file and backup that text file with the workspace.
Uninstall Ganymede.
Install Galileo.
In my case, the workspace had not been altered, and I pointed Galileo to the same workspace, so all my projects and files were still there.
Update all the plugins and extensions in Galileo from the update sites noted in the text file.
At this point I had some trouble because of outdated versions of plugins / incompatibility issues of plugins with Ganymede and Galileo. However, some minimal Googling helped me fix these issues.
Galileo was one of the cleanest and most straightforward installs I have ever done and I never had to mess around with eclipse.ini

Related

Eclipse does not restart in Ubuntu

I have Ubuntu 16.04 and Eclipse Oxygen 3.A installed on my machine. The Eclipse restart does not work. Eclipse closes but does not start again neither by 'Restart' menu nor if an application requires a restart.
Update: I cleared .metadata/.log and then restarted Eclipse from the menu. As usual Eclipse closed down but did not start again. I had to start it by clicking on the icon on my taskbar. Below is the logs generated when I started Eclipse.
!SESSION 2018-08-19 20:44:55.135 -----------------------------------------------
eclipse.buildId=4.7.3.M20180330-0640
java.version=1.8.0_181
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_IN
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
!ENTRY org.eclipse.ui 2 0 2018-08-19 20:45:05.372
!MESSAGE Warnings while parsing the images from the 'org.eclipse.ui.commandImages' extension point.
!SUBENTRY 1 org.eclipse.ui 2 0 2018-08-19 20:45:05.372
!MESSAGE Cannot bind to an undefined command: plug-in='org.eclipse.lsp4e', id='org.eclipse.lsp4e.togglehighlight'
!ENTRY com.genuitec.eclipse.theming.ui 1 0 2018-08-19 20:45:08.115
!MESSAGE A DevStyle Theme is being activated on this workspace; preparing colors and configuration
!ENTRY com.genuitec.eclipse.theming.ui 1 0 2018-08-19 20:45:09.652
!MESSAGE DevStyle has archived current color configurations to alternate preferences - will be restored when switching out of the DevStyle Theme
!ENTRY com.genuitec.eclipse.patches 2 0 2018-08-19 20:45:13.331
!MESSAGE Patches instrumentation extension PerformanceJavaNavigatorContentProviderPatch ([31078] [Angular] Webclipse UI freezes constantly after closing/reopening Angular 2 projects) has not weaved class org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider.
The issue was that the path set for --launcher.library argument in eclipse.ini file was incorrect. I found it out by comparing the ini files from another installation. The path for this argument was set as a relative path which I replaced with an absolute path as below.
/home/<username>/.p2/pool/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.700.v20180518-1200

STS freeze during build workspace on startup

I am running Spring STS 3.4.0 on Mac OS 10.8 with Tomcat 7, maven 3.1.1 installed, but almost everytime I start STS, try to open any project it freezes while building workspace at exactly 42%. By checking the log file, I found the following:
Can someone please tell me what is wrong and how I can possibly fix this problem?
Note: I don't have any firewall
Thanks
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:41.657
!MESSAGE Failed to retrieve plugin descriptor for
org.apache.maven.plugins:maven-eclipse-plugin:2.9: Plugin
org.apache.maven.plugins:maven-eclipse-plugin:2.9 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.apache.maven.plugins:maven-eclipse-plugin:jar:2.9
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:41.695
!MESSAGE Failed to retrieve plugin descriptor for
org.codehaus.mojo:exec-maven-plugin:1.2.1: Plugin
org.codehaus.mojo:exec-maven-plugin:1.2.1 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.codehaus.mojo:exec-maven-plugin:jar:1.2.1
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:42.178
!MESSAGE Failed to retrieve plugin descriptor for
org.apache.maven.plugins:maven-eclipse-plugin:2.9: Plugin
org.apache.maven.plugins:maven-eclipse-plugin:2.9 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.apache.maven.plugins:maven-eclipse-plugin:jar:2.9
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:42.194
!MESSAGE Failed to retrieve plugin descriptor for
org.codehaus.mojo:exec-maven-plugin:1.2.1: Plugin
org.codehaus.mojo:exec-maven-plugin:1.2.1 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.codehaus.mojo:exec-maven-plugin:jar:1.2.1
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:44.447
!MESSAGE Using platform encoding (US-ASCII actually) to copy filtered
resources, i.e. build is platform dependent!
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-02-09 16:04:44.525
!MESSAGE Using platform encoding (US-ASCII actually) to copy filtered
resources, i.e. build is platform dependent! !SESSION 2014-02-09
16:21:47.448 -----------------------------------------------
eclipse.buildId=3.4.0.201310051614-RELEASE-e43 java.version=1.7.0_45
java.vendor=Oracle Corporation BootLoader constants: OS=macosx,
ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product
org.springsource.sts.ide -keyring /Users/mkm/.eclipse_keyring
-showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.springsource.sts.ide -keyring
/Users/mkm/.eclipse_keyring -showlocation
!ENTRY org.eclipse.jface 2 0 2014-02-09 16:22:07.157 !MESSAGE
Keybinding conflicts occurred. They may interfere with normal
accelerator operation. !SUBENTRY 1 org.eclipse.jface 2 0 2014-02-09
16:22:07.157 !MESSAGE A conflict occurred for COMMAND+SHIFT+F10:
Binding(COMMAND+SHIFT+F10,
ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register
As Service, Adds class name to META-INF/services/%serviceType% file
after service type is selected in the dialog from types extended and
implemented by the class.,
Category(org.eclipse.ui.category.file,File,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler#241a8926,
,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system) Binding(COMMAND+SHIFT+F10,
ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show
System Menu, Show the system menu,
Category(org.eclipse.ui.category.window,Window,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler#4a22304e,
,,true),null), org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,cocoa,system)

TeXLipse install on Juno not working

I have tried to install the TeXLipse extension in Juno Eclipse, running on Ubuntu 12.04.
The installation goes off without a hitch however when I choose the project creation wizard TeXLipse is not there as an option. It is also not showing up in the Windows > Preference section of eclipse.
Has anyone else experienced this and have a suggestion on how to get this to work. I have googled around and other people have gotten it to work with Juno. I am just not sure what I am missing.
Thanks
Edit: Solution
I want to impart some details. I have the stock Eclipse install for Eclipse on Ubuntu. I then did an update where I simply replace the eclipse install located in /usr/lib/eclipse.
You can Google around for specifics.
To figure out what my system was doing I did two things.
Located in the ~/workspace/.metatdata folder is a file called .log. At the terminal I ran tail -f ~/workspace/.metatdata/.log so that I could watch the log files for any errors as I did the installation.
I ran eclipse from the terminal $> eclipse to see any errors were produced.
My first error was that eclipse could not fine ~/.eclipse file/directory when I ran eclipse. So I simply created this directory in my home folder and this error went away. I tried to install the plugin and I got a new error posted to the .log file:
!SESSION 2013-01-31 11:21:39.559 -----------------------------------------------
eclipse.buildId=M20120914-1800
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.equinox.p2.engine 4 4 2013-01-31 11:23:38.266
!MESSAGE An error occurred while committing the engine session for profile: epp.package.jee.
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-01-31 11:23:38.266
!MESSAGE
!SUBENTRY 2 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-01-31 11:23:38.266
!MESSAGE Error saving manipulator.
!STACK 0
java.io.FileNotFoundException: **/usr/lib/eclipse/eclipse.ini** (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:209)
at java.io.FileOutputStream.<init>(FileOutputStream.java:160)
at java.io.FileWriter.<init>(FileWriter.java:90)
at
org.eclipse.equinox.internal.frameworkadmin.equinox.EclipseLauncherParser.save(EclipseLauncherParser.java:321)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.save(EquinoxManipulatorImpl.java:378)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.save(LazyManipulator.java:97)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseTouchpoint.saveManipulator(EclipseTouchpoint.java:61)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseTouchpoint.commit(EclipseTouchpoint.java:137)
at org.eclipse.equinox.internal.p2.engine.EngineSession.commit(EngineSession.java:123)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:93)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174)
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:53)
The installer wanted to update the /usr/lib/eclipse/eclipse.ini. I changed the permissions on this to write all (the alternative is to run eclipse as root which I didn't want to do).
I uninstalled the plugin and re-installed it and now it works as intended. I hope this helps someone else. Don't forget to reverse the permissions after.
Eclipse seems to need write permissions to the place where you installed it. How I see it, this leaves you with two options:
Install (i.e., extract) Eclipse to a folder you own, for example your home folder.
If you installed Eclipse to /opt/eclipse owned by root, you also have to install plugins as root.
This question describes the same problem under Windows. This (German) website suggests option 2 from the above as solution.

Eclispe Helios Plug-in Development Target Platform Template Base-RCP broken?

I'm trying to create a standard osgi bundle under Eclipse Helios.
To do so, I've configured my Target Platform like this:
Window -> Preferences -> Plug-in Development -> Target Platform -> Add
After I choose Template and Base RCP (Binary Only)
I changed the name and clicked Finish.
When I launch the platform using the Overview of my bundle, I've got this error printed in the console :
!SESSION 2010-07-16 15:44:37.987 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -dev file:C:/Documents and Settings/E364866/Desktop/calendar/antonio osgi tutorial/.metadata/.plugins/org.eclipse.pde.core/OSGI DynaResume/dev.properties -os win32 -ws win32 -arch x86 -consoleLog -console
!ENTRY org.eclipse.ui 4 4 2010-07-16 15:44:44.659
!MESSAGE Unable to load UI activator
!ENTRY org.eclipse.ui 4 4 2010-07-16 15:44:44.659
!MESSAGE Unable to load UI activator
!STACK 0
I've managed to make the platform run by deselecting the org.eclipse.ui plug-in in the platform configuration window, but I don't understand why this plug-in is selected by default.
Quoting the comments in org.eclipse.ui.internal.WorkbenchPlugin:
// The UI plugin needs to be initialized so that it can install the callback in PrefUtil,
// which needs to be done as early as possible, before the workbench
// accesses any API preferences.
org.eclipse.ui plugin needs to load before your plug-in. You may fix this problem by giving it a start level less than your bundle's start level (which is probably set at default 4).

eclipse cdt tools installing error

I am trying to install the CDT plugin on an exisitng 32-bit installation of Eclipse on Ubuntu Jaunty. I've tried both web-update and standalone-package install and both fail with the following error-
Application Started: 4000
!SESSION 2009-10-05 21:24:55.947 -----------------------------------------------
eclipse.buildId=I20090611-1540
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -consolelog -debug
!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2009-10-05 21:25:28.172
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: !fwConfigLocation.equals(fwPersistentDataLocation)
!fwConfigLocation=/opt/eclipse-galileo/configuration
,fwPersistentDataLocation=/opt/eclipse-galileo/plugins/configuration
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:360)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:331)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:50)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.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)
!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-10-05 21:25:28.201
!MESSAGE An error occurred while uninstalling
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-05 21:25:28.202
!MESSAGE session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Uninstall, operand=[R]org.eclipse.ant.ui 3.4.0.v20090520 --> [R]org.eclipse.ant.ui 3.4.1.v20090901_r351, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-05 21:25:28.202
!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:54)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.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)
This may be related to bug 285743: as explained in this thread
What happens is that P2 fails to correctly setup osgi.install.area, because it doesn't strip 'plugins' part from the path. I saw this happen when eclipse.ini file in target directory didn't have '-startup' option in it.
Take a look into your eclipse.ini file if it contains -startup option like this:
-startup
plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
Note: if this is the case, you can refer to "proper" eclipse.ini to avoid any settings-related problem (for eclipse3.4 or 3.5.x): see "good" eclipse.ini.