If you want to build a Kieler product or the KiCo command line tool, you will need to use maven to build the project.
Commands should run from the semantics root directory.
If Java 11 is not your default java command prepend the following command (Linux) to set the java version: JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/
Hence it may look like: JAVA_HOME=/your/path/to/java mvn -f build/pom ...
It is recommended to add -T 2 as parameter to the following commands to speed up the build. However, it might be not helpful in some situations as the build log will be scrambled due to the parallel build threads.
|mvn -f build/pom.xml clean package -P semantics.test||Builds all plugins and CLI. CLI tools are located in build/de.cau.cs.kieler.kicool.cli/target/exe or sccharts.cli respectively.|
|mvn -f build/pom.xml clean integration-test -P semantics.test||Performs all tests (including CLI tests)|
|mvn -f build/pom.xml clean package -P semantics||Builds all plugins and creates the updatesite in build/de.cau.cs.kieler.semantics.repository/target/repository|
|mvn -f build/pom.xml package -P semantics.product||Builds the Kieler product and CLI. By default the build will use the plugins from the nightly updatesite, not the locally built plugins! Change the kieler.semantics.updatesite property in build/pom.xml to a file url (file://your/path/to/updatesite) leading to updatesite mentioned above. Do not commit this change!|