On 16-03-30 12:55 AM, Pradeep Balachandran wrote:
Sure Pascal. I agree. That's just a work around.A better approach is to tell load API not to cache the URIs in certain cases. Is there a way to do that?
No. There is no API to do this.
PradeepInactive hide details for Pascal Rapicault ---03/29/2016 09:11:12 PM---Note that it is highly recommended to use the API that NPascal Rapicault ---03/29/2016 09:11:12 PM---Note that it is highly recommended to use the API that Ned mentioned. Trying to directly tap into tFrom: Pascal Rapicault <[email protected]> To: P2 developer discussions <[email protected]> Date: 03/29/2016 09:11 PM Subject: Re: [p2-dev] API for "Available Software Sites" pref store Sent by: [email protected] ------------------------------------------------------------------------Note that it is highly recommended to use the API that Ned mentioned. Trying to directly tap into the underlying preference store could lead to troubles, especially when installations are more fancy (e.g shared installs).On 16-03-29 02:44 AM, Ned Twigg wrote: > But it has the side effect of adding those URIs to "Available Software Sites". Blech! I only use P2 in the context of an RCP application with a fully custom UI, I hope my application is not caching every URI it's ever been passed... Looking at the IRepositoryManager interface, looks like you could `getKnownRepositories(REPOSITORIES_ALL)`, and then call `removeRepository()` for each one. ᐧ Ned Twigg Lead Software Architect, DiffPlug LLC 949-264-3433 340 S Lemon Ave #3433, Walnut, CA 91789 On Mon, Mar 28, 2016 at 10:15 PM, Pradeep Balachandran <[email protected]_ <mailto:[email protected]>> wrote: Yes, we are already fetching remote repositories using p2 API. But it has the side effect of adding those URIs to "Available Software Sites". Either there should be a way to tell p2 API not to cache these URIs or those URIs have to be removed from "Available Software Sites". We couldn't find a way to do the former and hence the main focus of this email is the latter. Pradeep Inactive hide details for Ned Twigg ---03/28/2016 11:47:23 PM---I don't know anything about changing prefs for "Available SoftwNed Twigg ---03/28/2016 11:47:23 PM---I don't know anything about changing prefs for "Available Software Sites". But, it is definitely pos From: Ned Twigg <[email protected]_ <mailto:[email protected]>> To: P2 developer discussions <[email protected]_ <mailto:[email protected]>> Date: 03/28/2016 11:47 PM Subject: Re: [p2-dev] API for "Available Software Sites" pref store Sent by: [email protected]_ <mailto:[email protected]> ------------------------------------------------------------------------ I don't know anything about changing prefs for "Available Software Sites". But, it is definitely possible to fetch remote repositories using just the raw P2 API. This blog post does a pretty good job describing how._ __http://eclipsesource.com/blogs/tutorials/eclipse-p2-tutorial-managing-metadata/_ ᐧ Ned Twigg Lead Software Architect, DiffPlug LLC_ __949-264-3433_ <tel:949-264-3433> 340 S Lemon Ave #3433, Walnut, CA 91789 On Mon, Mar 28, 2016 at 3:58 AM, Pradeep Balachandran <[email protected]_ <mailto:[email protected]>> wrote: I would like to know whether there are APIs to get all entries and remove entries from "Available Software Sites" pref store. I can of course load up the p2 repository and look into the code (as mentioned in [1] ). Thought I will check here first. BTW, this is required because when WTP accesses adapters from the internet, those sites get added to this list which shouldn't be (see [2]). So, if there is a p2 API to fetch remote repositories without adding the URI to the "Available Software Sites" list, that should help too. In the absence of that we will need to deal with the pref store directly (via APIs). This query was posted on the forum [3] but no responses so far. [1] _https://www.eclipse.org/forums/index.php/t/38712/_ [2] _https://bugs.eclipse.org/bugs/show_bug.cgi?id=487917_ [3] _https://www.eclipse.org/forums/index.php/m/1726988/#msg_1726988_ Pradeep _______________________________________________ p2-dev mailing list_ [email protected]_ <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit_ __https://dev.eclipse.org/mailman/listinfo/p2-dev________________________________________________ p2-dev mailing list_ [email protected]_ <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit_ __https://dev.eclipse.org/mailman/listinfo/p2-dev_ _______________________________________________ p2-dev mailing list_ [email protected]_ <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit___https://dev.eclipse.org/mailman/listinfo/p2-dev________________________________________________ p2-dev mailing list [email protected]_ <mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit_https://dev.eclipse.org/mailman/listinfo/p2-dev________________________________________________ p2-dev mailing list [email protected]To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/p2-dev
