| Summary: | Errors upgrading shared install with install dir containing spaces | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | John Arthorne <john.arthorne> | ||||
| Component: | p2 | Assignee: | John Arthorne <john.arthorne> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | pascal, simon_kaegi | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.5 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 262433 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
John Arthorne
Here's the relevant snippet from the profile file. Note also the weird name of the installFolder property key.
<profile id='SDKProfile' timestamp='1232651687342'>
<properties size='8'>
<property name='org.eclipse.equinox.p2.cache' value='C:\Program Files\eclipse342'/>
<property name='org.eclipse.equinox.p2.flavor' value='tooling'/>
<property name='org.eclipse.equinox.p2.roaming' value='true'/>
<property name='org.eclipse.update.install.features' value='true'/>
<property name='org.eclipse.equinox.p2.environments' value='osgi.ws=win32,osgi.os=win32,osgi.arch=x86'/>
<property name='org.eclipsFo1e.equinox.p2.installFolder' value='C:\Program Files\eclipse342'/>
<property name='eclipse.touchpoint.launcherName' value='eclipse.exe'/>
<property name='org.eclipse.equinox.p2.cache.extensions' value='file:/C:/Program Files/eclipse342/.eclipseextension|file:/C:/Program Files/eclipse342/configuration/org.eclipse.osgi/bundles/69/data/listener_1925729951/'/>
</properties>
I think for backwards compatibility with 3.4.x we need to fall back to parsing an unencoded URL string from this property if we fail to parse as a URI. (In reply to comment #2) > I think for backwards compatibility with 3.4.x we need to fall back to parsing > an unencoded URL string from this property if we fail to parse as a URI. The code in simpleconfigurator might be good to use here as it has similar requirements. Tentatively marking for 3.5, however we should only worry about this if we want to support the update from 3.4 to 3.5. > we should only worry about this if we want to support the update from 3.4 to 3.5.
We've been selling this as a major advantage of p2 over UM, so I think we should support this upgrade unless there are severe technical problems doing it. This particular case is relatively simple and we have dealt with this exact problem in other places where we have migrated from URL to URI.
Created attachment 126038 [details]
Fix + tests v01
Fixed in HEAD. |