From 937fd46dc464ec4f7894609e965bb9e84ee2822c Mon Sep 17 00:00:00 2001
From: Eike Cochu <eike@cochu.com>
Date: Sat, 27 Feb 2016 18:20:31 +0100
Subject: [PATCH] updated build information
---
README.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/README.md b/README.md
index fa870e9b..29427d19 100644
--- a/README.md
+++ b/README.md
@@ -30,17 +30,17 @@ The following steps were reproduced in that order on a fully updated Ubuntu 15.1
* maven3: to install project dependencies
* Tomcat 8: a JavaEE application server
* gsl, gflags: for building dtm (see below)
+
```bash
sudo apt-get install openjdk-8-jdk mongodb git maven tomcat8 libgsl0-dev
```
- install a recent version of **nodejs** (the official repositories contain old versions)
+2. install a recent version of **nodejs** (the official repositories contain old versions)
```bash
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install nodejs
# gulp needs a node executable, ubuntu only creates a nodejs executable
sudo ln -s /usr/bin/nodejs /usr/bin/node
- bower inst
```
if watchman will be used (see below) additional packages are required for building watchman from source
@@ -48,12 +48,12 @@ The following steps were reproduced in that order on a fully updated Ubuntu 15.1
build-essential autoconf automake python-dev
```
-2. Install **required node packages** for frontend development
+3. Install **required node packages** for frontend development
```bash
sudo npm install -g bower gulp
```
-3. Build and install **watchman**. This step is optional but recommended, as nodejs watchers are less performant. This is only required if the `gulp watch` command will be used to continuously rebuild the frontend project assets.
+4. Build and install **watchman**. This step is optional but recommended, as nodejs watchers are less performant. This is only required if the `gulp watch` command will be used to continuously rebuild the frontend project assets.
```bash
git clone https://github.com/facebook/watchman.git
cd watchman
@@ -67,16 +67,16 @@ The following steps were reproduced in that order on a fully updated Ubuntu 15.1
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
```
-4. 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.
+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.
-5. Clone the project repository and build the projects
+6. Clone the project repository and build the projects
```bash
git clone https://somerepo.url/vipra.git
cd vipra
./build.sh
```
-6. 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.
+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.
```bash
cd dtm_release
make
--
GitLab