Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Required Software

In general, the most recent versions can (and should) probably be used for each of these. But the versions below are the ones I have working as of May 2019.

  • Java OpenJDK 11.0.2
  • Eclipse 2019-03
  • Git 2.9.0
  • Apache Maven 3.6.0
  • SQL Developer 3.2.20.09 (Not required for build, but useful for support)

Setup

Install the OpenJDK, Eclipse, git, and Maven normally. Modify your path as necessary so that you can run Maven and Java from the git bash shell.

Clone all of the git projects from the 'ras' and 'ras-kuali' groups on the Tufts GitLab (https://gitlab.it.tufts.edu/rashttps://gitlab.it.tufts.edu/ras-kuali).

 

Build Process

Detailed instructions for building the Kuali Coeus software can be found in the Kuali git repo at https://github.com/KualiCo/kc/blob/master/README.md

The basic steps for building the Tufts release are to run the maven build in each of the following projects using the given commands:

  1. schemaspy – mvn clean install -Dgrm.off=true
  2. kc-rice – mvn clean install -Dgrm.off=true
  3. kc-api – mvn clean install -Dgrm.off=true
  4. kc-s2sgen – mvn clean install -Dgrm.off=true
  5. kc – mvn clean install -Dgrm.off=true
  6. kc-custom – ./build.sh

The "-Dgrm.off=true" flag is necessary to disable the proprietary parts of the Kuali builds. If the flag is not provided, the build will fail while attempting to download artifacts from the private internal Kuali repo.

Each build in steps 1-5 will create the jar/war file for that project and store it in your local maven repository. The final step will create the final application .war file at kc-custom\coeus-webapp-custom\kc-dev.war. This file should be uploaded to the tomcat\webapps directory to deploy and run the KC application.

 

 

  • No labels