Page History

...

The following build profiles are available in the KIELER Semantics repository:

...

What to Be Aware of

There are some things that people need to be aware of to keep the build files in a valid state.

1. Eclipse metadata and POM files are not synchronized. Thus, if the version of an Eclipse plug-in changes, its pom.xml needs to be updated accordingly.
2. The repository POM directories contain product files and product icons. These are copies of the files found in the corresponding branding plug-ing (such as de.cau.cs.kieler.core.product) and have to be manually synchronized.

The Curious Case of Building the KLay Library

We distribute our KLay layout algorithms in two library files: one that contains just our algorithms, and another one that also contains dependencies such as required EMF classes. To build the KLay libraries, navigate to the /build/de.cau.cs.kieler.klay.libraries directory and do the following:

1. Set the TARGET_PLATFORM environment variable to point to a local copy of our currently used target platform p2 repository. Ask Unknown User (cds) where you can get that.
2. Set the KIELER_REPOSITORY environment variable to point to a local copy of a p2 repository of our pragmatics build. Again, ask Unknown User (cds) where you can get that.
3. Run Ant on the build.xml file. This will produce both versions of the KLay layout library.

...

1. .

Continuous and Nightly Builds

...

Our automatic builds produce a bunch of so-called artifacts: redistributable applications as well as a number of update sites. This table lists all artifacts, the project or repository they belong to, the build file responsible for producing them, the Bamboo build plan that builds them, and the directory they are finally placed in.