Community
Participate
Working Groups
Build Identifier: 3.6.2 The P2 configuration does not appear to respect what the name of the configuration directory is called. From a vanilla RCP install, with update capabilities (or in general, any Eclipse installation), rename the configuration directory to something else, say, conf. Start Eclipse with -configuration conf Perform an installation of a new feature with P2 The P2 update mechanism writes out configuration\config.ini, which contains the list of bundles that are installed When Eclipse restarts, although P2 claims the features are installed, the bundles aren't listed because they're being written to a directory which P2 isn't updating The top of the config.ini file is: #This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser Reproducible: Always
(In reply to comment #0) > Start Eclipse with -configuration conf Is this just on the command line, or is it in the eclipse.ini?
This was from the eclipse.ini file - however I had renamed it (and the executable) to eclipse32.ini/exe.
It is possible that the rename could be the source of the problems. Bug 299955 is an example where things go wrong on Mac when the Eclipse.app folder is renamed. (I haven't had time yet to try things myself).
If I look in Help -> About box, the startup configuration clearly shows -configuration conf, so it's visible. I'm not sure why it would be trying to read the .ini file anyway - the (selected) updates don't change the content of that. Either way, it shouldn't be using what's in that file to find the configuration directory, because it could be overridden on the command line in any case.
Not to say that there is no bug here, but the eclipse.ini is read to figure out all sorts of information about how the installation is actually setup, so not having it means that defaults are used that do not necessarily match the running system. If you try the same operation without changing the eclipse.ini does it fails or succeeds?
I have two products installed in the same directory, which is why I need two different file names ( and two different configuration directories) so renaming is not possible.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
