Skip to main content
Jump to: navigation, search


< CBI‎ | aggregator
Revision as of 08:40, 27 April 2010 by (Talk | contribs) (Installing Eclipse and the Aggregator)


Note: This page is copied from the Buckminster Aggregator and is currently being refactored.

Installing Eclipse and the Aggregator

  1. Start by installing a fresh Eclipse 3.6 SDK from (The latest version used at the time of writing was
  2. Start your Eclipse installation and open the Install New Software wizard. You'll find in under the top menu Help
  3. Click the Add... button and enter the URL in the Location field.
  4. Select the b3 Aggregator Editor and click Next twice.
  5. Accept the Eclipse Public License and click Finish
  6. Restart the IDE once the installation is finished.
Install New Software wizard
b3 Aggregator Editor selection

Creating your first aggregation

  1. Create a new empty project. Here it's called aggregation.example but any name will do.
  2. Right click on the project and choose New -> Other... to bring up the New wizard.
  3. Select Buckminster -> Aggregator Model and click Next
  4. Name the aggregation. Here it's called Note that the name must end with .build
  5. Click Finish. That will bring up the Aggregation Editor on an empty model.
  6. When working with the model, it is essential that you see the Properties view. You open this view by right-clicking on the top resource (the one labeled platform:/resource/aggregation.example/ and select Show Properties View in the pop-up menu.
New Aggregator Model wizard

Add a Configuration

New Configuration

In order for validation to take place, you must add platform configurations to the model. You can start by adding a configuration that contains the default values. Expand the top resource and right click on the Aggregation element. Select New Child -> Configuration.

The result of adding a sample configuration of type Operating System = win32, Windowing System = win32, Architecture = x86 is shown in the screenshot.

Note that you can add as many configurations as you want, it may however be the case that they are recognized as invalid or dependencies cannot be satisfied during the aggregation process.

Add a Contribution

Everything that is mirrored is based on Contributions. A Contribution defines one or several P2 repositories to include in the aggregation. You may also specify one or several contacts that will receive emails when problems are encountered that can be associated with the contribution. The contacts are optional. If no one is specified and an email needs to be sent, that email will be sent to the buildmaster.

You add a Contribution the same way that you added the Configuration.

Adding a P2 repository

Adding repositories

Once a contribution is added, you can add a MappedRepository to it. Again by right clicking and selecting New Child. The repository has some properties that will become visible and editable in the Properties pane. Type a URL to a valid repository in the Value column of the property named Location and hit return. A short delay where the UI feels locked is to be expected here since the repository is loaded. A sample is shown in the screenshot.

Adding content to the repository

A repository can either be mapped verbatim, in which case you cannot make any changes to categories or, it can be mapped piece by piece. A piece in this case is a category, a feature, a product, or a bundle.

Mapping verbatim

You can map a whole repository as it stands by just adding it to the contribution. You can also specify an optional category prefix which is automatically added to each category label from the original repository.

Choosing specific content

Adding repositories

You can map specific categories, features, products, or bundles from a repository by adding them as children. When you add a child, you bind it to one of the features present in the repository denoted by the parent. Like this:

  1. Right click on the Mapped Repository and select New child (if this choice is not available in the menu, you probably have the Map verbatim flag set to true).
  2. Put your cursor in the Installable Unit value field in Properties tab. It now turns into a drop-down box.
  3. Select the feature that you want to map and hit enter.
  4. The feature can be added to an added category. Such categories can be added after they have been added to the top node, i.e. right click on the Aggregation and choose New Child and then Custom Category

Other types of content can be added the same way. We plan to make it possible to add a category with a rename option in a coming iteration. At present, categories can only be mapped verbatim and you have to create a Custom Category and add features to it manually in case you want another name.

Running the aggregation


Running the aggregation

Before you run the aggregation, you must make sure that it contains all features that you intend to map along with all their dependencies. The validation will fail unless the repository is self sufficient therefore it might be a good idea to map the Eclipse Platform repository or the repository that represents the Galileo Release.

Also make sure that the Aggregation and its contributions have labels and that you save the model (ctrl-s) before you run. The labels are required.

Starting the aggregation build

Running is easy. Simply right click on the top node in the tree and choose Build Repository. It should take a while. If it doesn't, the you need to bring up the Error log and check what happened (subject to improvement of course). If the Error Log is not already present (as a tab in the same window as the Properties), you will find the errors view by clicking Window on the top level menu of your IDE, select Show View and then Error Log

Where to find the result

The result of the build should end up $HOME/build where the final repository is in the folder named final.

Back to the top