Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Org.eclipse.ecf.sdk.cquery
Return to Building ECF Release 3.2
The cquery files work with the rmap file. For your queries to resolve against repositories (source code or binary), you need to construct a Buckminster Resource Map (rmap) (Bucky Book, page 46).
What's inside the cquery file? You can use the Component query editor (part of Eclipse's Buckminster plugin) to view the cquery file. Or you can just read and edit the xml.
- Identify the rmap if you are using one (we are).
- Give the component a name (org.eclipse.ecf.sdk) and a type (eclipse.feature).
- We are not specifying a version designator. I mean we specify ?==Version but then we do not identity Version.
- Note that target.arch, target.os, and target,.ws have values of *. These values may become important later when we figure out how to use different target platforms.
- Lots of advisor nodes. These provide advice to the Buckminster resolution process.
Order is important for the advisor nodes. An advisor node is identified by a name pattern, which “is a regular expression pattern that is used to select the components that should receive the advice provided in the advisor node. “ (Bucky Book, page 50).
org.eclipse.sdk,cquery has six advisor nodes. The first five specify that components matching the patter do not use a target platform (exactly what does this mean) and do not use a workspace (for what? ... rsolution?). The last advisor node (.*) rejects any component not matched by a previous advisor node.
Here's the latest version of the org.eclipse.ecf.sdk.cquery file.