Reminder: Do not include any PHI or PII in Confluence. If you require 508 accessibility assistance or any other support for this system, then please send an email to onc-jira-questions@healthit.gov
...
See the System and Software Requirements Guide for instructions on how to prepare your system prior to installation of the validator.
Warning |
---|
The dependent Maven projects must be built from their sources prior to building the CRV Maven projects. See the Code Validator Guide for instructions. |
Building CRV
The following steps are for checking out the release tag and building the source code. The Code Validator project must be built prior to building CRV.
Checkout the Sources
1) Use the Git CLI to checkout the desired version.
To clone the repository and checkout the tip (newest revision of the default branch), run the following:
git clone https://github.com/esacinc/crigttCDCgov/cancer-report-validator.git ~/crigttcancer-report-validator
Typically, the latest stable release tag should be used for deployments. To checkout this tag, run the following:
cd ~/crigttcancer-report-validator
git checkout crigtt-v1.1.0.2-RELEASE1
Build the Projects
To build all of the Maven projects, run the following:
cd ~/crigtt/cancer-report-validator
mvn -DskipTests=true
Developer Functionality
The following sections describe advanced functionality typically reserved for developers.
Checkout the Sources for Development
To checkout the trunk for development from GitHub, you should create a GitHub account and fork the CRV project repository at https://github.com/esacinc/crigtt to your account.
Then, checkout your forked version of the repository, by running the following:
git clone https://github.com/<your username>/crigtt ~/crigtt