| RE: [mdt-ocl.dev] Orbit Map File references |
|
Hi Ed, Adolfo,
I also think it won't affect us.
Should we be 'including'
rather than selectively pasting orbit.map?
I
don't know how to include map files. However, if this is possible it would be
good to refer to the source map.
Should we be using a map p2UI rather than GET operation? I
agree with Adolfo - I think using GET is a good
decision.
Regarding Buckminster, no, I haven't looked at it yet.
But I think we definitely shouldn't adopt it in
Helios.
Regards,
- Alex.
From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink Sent: Thursday, April 29, 2010 8:27 AM To: MDT OCL mailing list Subject: [mdt-ocl.dev] Orbit Map File references On 27/04/2010 10:30, Adolfo Sánchez-Barbudo Herrera wrote: David Williams wrote on cross-project-dev We in Orbit are considering (will, unless there's quick complaints) to change the URL of our p2 repositories produced with our builds. From ending with "updateSite" to "repository". I'm 99% sure this won't effect anyone, since I'd think anyone who currently uses it, uses our "p2 maps" generated during a build; hence you may not even know it ever was "updateSite" :) and you'll just get the change automatically when you get a new p2 map file. This would effect only "future" repository URLs ... we not changing anything that exists. -- I'm not quite sure what this means. We don't seem to be using the "updateSite" so I don't think it affects us. However we're also not using the expected p2 map file directly. Should we be 'including' rather than selectively pasting orbit.map? Should we be using a map p2UI rather than GET operation? Ed |