Update Build branches

• Build order for the projects is at the top of the build instructions here: https://github.com/KualiCo/kc/blob/master/README.md
  • The typical order is schemaspy > kc-rice > kc-api > kc-s2sgen
• For each project in order, do the following:
  • Open Git Bash in the project folder
  • git remote -v
    • Verify that the KualiCo repo is added as a remote, e.g. https://github.com/KualiCo/kc-s2sgen
  • git checkout master
  • git fetch github
    • This will pull down all new tags from the KualiCo repo
  • Check the KC master POM file to find the current required version number for each project (it's not always the latest version needed): https://github.com/KualiCo/kc/blob/master/pom.xml
  • git checkout <tag for project version that matches the KC POM file>
    • e.g. git checkout coeus-s2sgen-1901.0001
  • Add the tag to the RAS Current Build Branches wiki page: RAS Current Build Branches
  • Build the project:
    • mvn clean install -Dgrm.off=true
  • Push the tags up to the Tufts GitLab repo:
    • git push --tags
• Repeat these steps for each dependent project.
• Once all dependent projects have been built, the 'kc' project should be built next. Follow the same steps as above to fetch the new tags and checkout the most recent release tag. However, instead of doing a simple 'mvn clean install', use the following commands to build the project:
  • export VCTargetsPath="C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120"
  • mvn clean compile source:jar javadoc:jar install -Dgrm.off=true -P oracle