Eclipse updating indexes android
Thankfully, the development server can determine the index configuration for you.
To use automatic index configuration, add the attribute , then disable automatic index configuration and test your app in the development server.
It is simply a property file, listing the type of repositories supported and the order they should be tried: This example instructs the p2 client to use the OBR format if it understands it, otherwise it should fall back to the standard XML file.
If it can´t read either of these two, it should give up because there is nothing else here.
p2 doesn´t know anything about the different formats, and when instructed to load a repository at it will simply cycle through each format which has been contributed, looking for metadata (content.jar, composite Content.jar, maven Artifacts.mvn, obr Repository.obr, etc/). What if you want to control the order in which p2 searches?
More importantly, what if you want to control the order and offer a fall-back (Use the OBR format if the client can read it, otherwise use the standard format)?
If the app performs a query that requires an index that hasn't finished building yet, the query will raise an exception.
You specify which indexes your app needs in a configuration file.Some people have suggested we just remove the file, or combine all the p2 related files into a single file (site.xml? While this might plug the current leak, it will most likely lead to problems elsewhere.Like most things, the introduction of this file was done to solve a problem. To help understand the p2.index file, it´s important to understand p2.Furthermore, what if you want do dynamically change the repository format?These are server configuration problems, that is, it´s up to the server administrator (not the client) to give advice about what repository formats are supported. The p2.index file is the first file p2 reads, and it gives advice to the client about what repositories exist on the server.