Community
Participate
Working Groups
Build Identifier: I20100608-0911 When invoking eclipse from command line eclipse with -configuration <config path> I experimented the following behaviour When started the first time the the "Help"-> "About" -> "Installation Details" shows just one line Once installing new software via "Help" -> "Install new software" -> "Add..." -> choose an online update site After the restart in the <config path> direcotry is generated the eclipse.ini.ignored file Reproducible: Always Steps to Reproduce: 1.Call eclipse with -configuration <config path>(or osgi.configuration.area in config.ini) 2.Check "Help"-> "About" -> "Installation Details" shows just one line (Is this correct?) 3.Install new software via "Help" -> "Install new software" -> "Add..." -> choose an online update site 4.Restart 5.Under <config path> an eclipse.ini.ignored file is generated with this content -startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -configuration ../../../Documents and Settings/culcasis/.stworkbench/helios/STW_SDK/configuration -vmargs -Xms40m -Xmx384m
Moving to p2. I think the engine is doing this, not sure if it is by design or not.
Hi Salvatore, This is all expected. When you run using -configuration your configuration information cascades back to the parent. This is also sometimes called a shared install because your are re-using the parent's bundles. Because you are sharing the parent's bundles I would strongly suggest you make those folders read-only. In the user install you just see the parent's installation "roots" and in your case it looks like there is exactly one. The eclipse.ini.ignored in the user configuration folder is "really" ignored and is generated mainly as a trace mechanism to help the p2 team sort out bizarre installation layouts.
