Community
Participate
Working Groups
Build Identifier: Indigo M5 If I use the director application to create an installation from scratch, the installation will have roaming disabled (despite -roaming) if I pass a relative path as -destination. Interestingly, the roaming property is first set to be true, but in the latest version of the profile it is false. I suspect that the logic that keeps the org.eclipse.equinox.p2.installFolder property in sync with the actual installation location chokes on the relative path set as installFolder, and as a consequence disables roaming. This leads to two possible ways to fix this issue (but I don't know with one is better): - Make the installFolder update logic cope with relative paths. - Have the director write an absolute installFolder in the first place. Reproducible: Always Steps to Reproduce: 1. Install a product, e.g. the Eclipse SDK with the -roaming parameter and a relative destination; Example command line: ./eclipsec -nosplash -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/releases/indigo/ -installIU org.eclipse.sdk.ide -profile DemoProfile -profileProperties org.eclipse.update.install.features=true -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming -destination ../testinstall 2. Open the profile in the resulting installation; in the example, the newest file in ../testinstall/p2/org.eclipse.equinox.p2.engine/profileRegistry/DemoProfile.profile/ It contains <property name='org.eclipse.equinox.p2.roaming' value='false'/>
Moving off 3.7, I don't have the time to investigate. See also bug #344153
Not going to make 3.7.1. Deferring.
Since there is nobody assigned, this will not be in 3.7.2.
Unsetting old milestones
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.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
