Pascal, I think so. List of update sites is my backup if I don't succeed running proper install actions (see nearby thread). What I need is to auto-configure my plugin when it's isntalling from update site, knowing the address of that site. If don't succeed in that, I'll implement looking through a list of update sites and searching for site that could have contained my plugin (this thread).
I think possible dirty way for 3.5 is to search for update sites on disk store in preference file manually. Thanks, 2011/3/30 Pascal Rapicault <[email protected]>: > 3.5 had no API. > The only way is to reach in the internal. > > Otherwise, on the 3.6 side, did you find everything you were looking for? > > On 2011-03-28, at 4:50 AM, Andrey Razumovsky wrote: > >> In fact, I can't find solution for 3.5 at all, since the API is closed >> all over (e.g. related classes IRepositoryManager, >> IMetadataRepositorymanager, RepositoryManipulator etc. are all >> internal) >> >> 2011/3/28 Andrey Razumovsky <[email protected]>: >>> 2011/3/25 DJ Houghton <[email protected]> >>>> >>>> 2). In older versions of Eclipse you can get the service through the >>>> bundle context and not go through the agent. Like you said, the agent was a >>>> concept introduced in 3.6. >>>> >>> Could you please provide a snippet? The following returns null: >>> context.getServiceReference(IMetadataRepositoryManager.class.getName()); >>> What service should I look for? >>> Thanks, >>> Andrey >> >> >> >> -- >> Andrey >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > -- Andrey _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
