Table of Contents |
---|
Testing Plan
Before In the course of testing, please review the VIVODOC112x.
Cloning the release candidate from GitHub
Note |
---|
Until version 1.12.0 reaches final release status, it will not be available from a Maven repository. |
Note |
To test the release candidate of VIVO 1.12.0, you will need to build the correct versions of a local copy of the source code for four projects: Vitro-languages and , VIVO-languages even if you only use VIVO in American English., Vitro, and VIVO. The instructions below show how to obtain the proper source code either using git or by direct download. |
Step 1: Obtain the source code
Option 1: clone the release candidate from GitHub
Clone the rel-1.12.0-RC branch of the four required GitHub projects into parallel directories. Then build Vitro-languages and VIVO-languages.
Code Block |
---|
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro-languages.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/VIVO-languages.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro.git
|
Option 2: direct download
Download the four rel-1.12.0-RC source code bundles (not "installer" files) and unzip/untar them into parallel directories:
https://github.com/vivo-project/Vitro-languages/releases/tag/rel-1.12.0-RC-1
https://github.com/vivo-project/VIVO-languages/releases/tag/rel-1.12.0-RC-1
https://github.com/vivo-project/Vitro/releases/tag/rel-1.12.0-RC-1
https://github.com/vivo-project/VIVO/releases/tag/rel-1.12.0-RC-1
Step 2: Build Vitro-languages and VIVO-languages
Code Block |
---|
cd Vitro-languages mvn install cd ../VIVO-languages mvn install |
...
Then proceed with the rest of the VIVO installation or upgrade according to the VIVODOC112x. Be sure that if from the Installing VIVO#PreparingtheInstallationSettings.1 step. If you are testing a clean installation, be sure to supply an empty vivo-dir in your settings.xml file. If you are testing an upgrade, make a copy of your existing VIVO 1.11 vivo-dir directory and supply the location of that copy as the value of vivo-dir in your settings.xml file.
...