[news.eclipse.technology.equinox] Re: Specifying initial repositories fo

[Ben Vitale <bsv@xxxxxxxxxxx>]

Sorry. I just saw the thread "I have managed to deploy p2-ed product 
using P2 installer from my repository whi". I think that describes what 
I need. Feel free to jump in, though, if its not.

Ben Vitale wrote:
> In the legacy update manager, one might set the Update Site URL on a 
> particular feature, and then it would know where to go to find updates 
> for that feature. This was important in enabling the Automatic Updates 
> feature.
>
> Now we're using p2, and I'm not sure how to accomplish the same thing. I 
> did find something on this page: 
> http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application
>
> --
> "The repositories that should initially be present in the application 
> can be controlled using touchpoint instructions. The addRepository 
> instruction should be used for each repository."
> --
>
> But then I also discovered this caveat:
>
> http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions#Where_the_touchpoint_advice_file_can_be_used 
>
>
> --
> "In Eclipse 3.5, touchpoint advice files can be placed: .... In products 
> (a p2.inf file co-located with the .product file): The instructions are 
> added to the root installable unit for that product. "
> --
>
> That sounds like what I want. But obviously I need to do this on 3.4.1. 
> Is there a workaround, or a manual way to inject a "default update site" 
> (e.g. metadata/artifact repo) for a product IU so that the product can 
> be shipped with Automatic Updates turned on?
>
> Thanks
> Ben