5. Install **Eclipse EE**. A different Java development IDE (or none at all) can be used, but the Vipra projects are made with eclipse and come with settings and run configurations. Install the M2Eclipse plugin for maven support in eclipse, if not yet installed. The plugin will download the required project dependencies and manage the project configurations, build versioning and packaging. Set up the installed Java EE application server in Eclipse. Add the `vipra-backend` project to the web server.
6. Install **Eclipse EE**. A different Java development IDE (or none at all) can be used, but the Vipra projects are made with eclipse and come with settings and run configurations. Install the M2Eclipse plugin for maven support in eclipse, if not yet installed. The plugin will download the required project dependencies and manage the project configurations, build versioning and packaging. Set up the installed Java EE application server in Eclipse. Add the `vipra-backend` project to the web server.
6. Clone the project repository and build the projects
7. Clone the project repository and edit the build.sh script
```bash
```bash
git clone https://somerepo.url/vipra.git
git clone https://somerepo.url/vipra.git
cd vipra
cd vipra
nano build.sh
```
make sure the 'TOMCAT_WEBAPPS' path points to the webapps directory of the Tomcat installation, if you want the WAR file to be deployed automatically.
to build the projects, run:
```bash
./build.sh
./build.sh
```
```
7. Build **dtm binaries**. The repository was added to the vipra project because the original repository is/was hosted on [Google Code](https://code.google.com/archive/p/princeton-statistical-learning/downloads). Refer to dtm_release/README if problems during the build arise.
if auto deployment is disabled to the path to the webapps directory is wrong, you need to manually copy `./vipra-backend/target/vipra.war` to your servers web application directory.