| Summary: | p2 director ignored bundlepool when using -roaming | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Paul Webster <pwebster> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | aniefer, bugs.eclipse.org, jeffmcaffer, remy.suen | ||||
| Version: | 3.6.2 | ||||||
| Target Milestone: | 3.7 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| URL: | http://alblue.bandlem.com/2011/04/multiple-architecture-single-build.html | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Paul Webster
you were using 3.6.2 right? (In reply to comment #1) > you were using 3.6.2 right? Right,org.eclipse.sdk.ide=3.6.2.M20110210-1200 PW This worked for me when I tried it on the latest 3.7 I think this is related to the -roaming, I didn't have that in my test. By inspection, DirectorApplication#updateRoamingProperties looks suspicious, it will change the PROP_CACHE (ie the bundlepool) to the destination. I think it needs to consider the bundle pool here. Work around is to not specify -roaming, this will make it so the resulting install is not able to be moved around after the fact. Created attachment 192869 [details]
patch
Patch uses the same logic as when the PROP_CACHE was set initially.
OK, with no -roaming I have the same results. eclipse.p2.data.area=file\:/opt/local/eclipse/dirExp37/eclipse/p2/ gets the absolute path, but my platform version launches no problem. PW I released this patch. With this fix, the bundle pool is now indeed shared. But -roaming is still broken, as there are absolute paths in the eclipse.ini and configuration/config.ini: eclipse.p2.data.area=file\:/opt/local/eclipse/I20110427-1300/target/p2 In a normal install: eclipse.p2.data.area=@config.dir/../p2/ PW -install /opt/local/eclipse/I20110427-1300/target/linux_gtk_x86_64 is the extra eclipse.ini line that is written. Should I open a new bug? PW I opened bug 344155 and bug 344153 PW |