Ecf.rmap

For a Buckminster build, the first thing to set up is an rmap. ecf.rmap is the rmap file that we use with the ECF SDK.

Now it works just fine, but I think there is extraneous information in it. It would be good to know exactly what is needed and what is not. Search path (org.eclipse) has providers (eclipse.import, PDEMapProvider). This is where we get the eclipse plugins that come with the platform. Why do we need PDEMapProvider here? Search path (org.eclipse.emf) has providers (eclipse.import, PDEMapProvider). Why do we need this? Why do we need PDEMapProvider here? Search path (org.eclipse.ecf) has provider (local). This is where we get the ECF code. Seach path (org.pluginbuilder) has provider (eclipse.import). This is not currently used. Search path (org.eclipse.swtbot) has provider ( (eclipse.import). Is this used? Is this for testing purposes, which are not yet doing. Search path (default) has providers (eclipse.import, PDEMapProvider). This is where we get the stuff from Orbit. Why do we need PDEMapProvider here? Without a resource map, Buckminster can only find resources in the Eclipse IDE. What does an rmap do? It defines searchpaths, providers and locators. The locators appear at the end of the file, but they really are the first things used. When Buckminster looks for a component, it goes through the locators in the order in which they are defined. Go to locators to see how the locators are defined. Here is an example of a locator. The locator matches a pattern. What this locator does is get everything in org.eclipse.ecf. The pattern ^org\.eclipse\.ecf(\..+) is explained on page 29 of the Bucky Book.