Skip to main content
Jump to: navigation, search

Difference between revisions of "Getting Started With Aggregator (Buckminster)"

(Adding content to the repository)
Line 42: Line 42:
# Put your cursor in the ''Installable Unit'' value field in ''Properties'' tab. It now turns into a drop-down box.
# Put your cursor in the ''Installable Unit'' value field in ''Properties'' tab. It now turns into a drop-down box.
# Select the feature that you want to map and hit enter.
# Select the feature that you want to map and hit enter.
More to follow...
More to follow...

Revision as of 01:49, 29 June 2009

Installing Eclipse and the Aggregator

  1. Install a fresh Eclipse 3.5 Platform from this location
  2. Start the Eclipse and open the Install New Software wizard. You'll find in under the top menu Help
    Buckminster Install New Software.png
  3. Click the Add... button
    Buckminster Add Site.png
  4. and enter the URL in the Location field. has had major infrastructure problems over the weekend. The material that was published on Friday is still not fully available on all mirrors. So right now you need to use the update site at instead.
    Buckminster Install Aggregator.png
  5. Select the Buckminster Aggregator Editor and click Next twice.
  6. Accept the Eclipse Public License and click Finish
  7. Restart the IDE once the installation is finished.

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.
    Buckminster New Wizard.png
  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.

Add a 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 should now look like this: Buckminster Aggregation Added Config.png

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

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. If successful, you should now see this: Buckminster Aggregation Added Repository.png

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 a whole repository just as it stands by setting the map verbatim flag to true. When you do, all nodes beneath the repository will be hidden since they no longer have any meaning (they will reappear if you set map verbatim to false again).

Choosing specific content

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.
    Buckminster Select Feature.png

More to follow...

Back to the top