Draft Build Specification

This is the place to capture the requirements for a automated build process for the Higgins project.

Initially the builds will only be available as Java Eclipse plugins.

In the long term we've publicly committed to also support these three package managers:

• RPM & Debian (for Suse, Red Hat, Debian, Ubuntu)
• OSX
• Windows

The download pages need to make it clear what platforms the binaries are for. (Note The Eclipse folks said that they are working on automated build scripts for the Eclipse IDE to target RPM and Debian package managers. Don't know about OSX.

What we need for the Eclipse download page:

• 1)We need automated build scripts for each separate "singleton" Higgins component that execute on build.eclipse.org (I think that's tne name of the build server) and create their own separate sections on the download page(s). What I mean by singleton is a component of which there is one and only one (shown in the diagram as NOT having a second gray box behind it and slightly offset).

There should be NO components on the Higgins download page that don't line up with the Core Component Architecture. See the Component Inventory http://wiki.eclipse.org/index.php/Component_Inventory. Each element in the Component nventory needs to be automatically built (with javadoc) and automatically tested (on build.eclipse.org) in three variants (daily, stable, release

• 2) Similar to 1) above, for components of which there will be N instances (non-singletons) (E.g. Context Provider plugins, or I-Card Provider plugins, or Token Provider plugins) there needs to be separate build scripts for each one. And a separate place on the downloads page.

• 3) Version numbers should line up with milestone (we're in M0.6 at present).

• 4)The .psf files (one for each Higgins component also need to be made available)

Next action item:

• Determine the target CPU list is (I only have x86 for now, we'll see what the dev call discussion brings)

• Present a template for the downloads page with dummy content. Someone Mary or Valery need to decide who is creating the template for this page as well as its static content.

• Create a build script for org.eclipse.higgins.idas that will run on build.eclipse and that will, every night, build a new version. As components are added (e.g. the org.eclipse.higgins.sts that MikeM is going to contribute) we will create scripts for them.

• HBX also lines up with the component architecture and should be covered by the nightly build process. HBX needs to be on its own separate download page as there will be many end users who will only need this piece. This page needs to be able to be used by somjeone who is not an Eclipse engineer. There should be a link to this page from the main downloads page.

• (Jena-based) Context Provider will be the second component that is built every day