VIVO Documentation
...
Code Block | ||
---|---|---|
| ||
$ git clone https://github.com/vivo-project/Vitro.git Vitro -b rel-1.12.0-RCmaint $ git clone https://github.com/vivo-project/VIVO.git VIVO -b rel-1.12.0-maint $ git clone https://github.com/vivo-project/Vitro-languages.git Vitro-languages -b rel-1.12.0-maint $ git clone https://github.com/vivo-project/VIVO-languages.git VIVO-languages -b rel-1.12.0-RC $ ls -lmaint drwxr-xr-x user group 1 Dec 12:00 Vitro drwxr-xr-x user group 1 Dec 12:00 VIVO drwxr-xr-x user group 1 Dec 12:00 Vitro-languages drwxr-xr-x user group 1 Dec 12:00 VIVO-languages |
Note |
---|
If you do not place the Vitro code in a sibling directory called "Vitro", then you will have to supply the "vitro-core" property to Maven - e.g. mvn package -Dvitro-core=~/Vitro It is expected that the Maven project numbers are kept in sync between the Vitro / VIVO projects, however, depending on when you update / sync your repositories, you may need to adjust the project version numbers for the build to work. |
...