Carry out a complete VIVO installation from scratch in order to identify any problems related to the installation process
https://wiki.lyrasis.org/display/VIVO/Release+Testing+-+1.12.0
Description | Value |
---|---|
Installation OS | Linux 5.4.0-73-generic #82-Ubuntu x86_64 x86_64 x86_64 GNU/Linux |
Java JVM | java -version |
Maven | Apache Maven 3.6.3 |
Home directory installation | ~/TEST-VIVO |
Action | Description | Result | ||
---|---|---|---|---|
1 | Making git-fork of VIVO Repo's to | |||
2 | Cloning all repo branche |
| ||
3 | Configuring settings.xml | <settings xmlns="http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
4 |
| rm -r ~/.m2/* |
In this scenario. the packages of (VIVO and Vitro) languages are previously compiled before the execution of Maven in the directory VIVO/installer
Action | Description | ||
---|---|---|---|
1 | Installing Vitro-languages | cd ~/TEST-VIVO/Vitro-languages | (This step generates a lot of download of Maven -Central because of the (~/.m2) directory cleaning ) |
2 | Installing Vivo-languages | cd ~/TEST-VIVO/VIVO-languages As you can see the packages are installed in the subdirectory (1.11.2-SNAPSHOT) of Maven (~/.m2) | |
3 | Installing VIVO | cd ~/TEST-VIVO/VIVO/installer/ |
All comments come from the analysis of the log file captured during the installation of VIVO (Pojnt 3)
Action | Result | Comments | |
---|---|---|---|
1 | grep -i SNAPSHOT vivo_install.log Filter on SNAPSHOT to evaluate the processed version |
| |
2 | Check if the files are properly installed in tomcat cd /opt/tomcat/webapps/ ; find . | grep fr_CA | OK | |
3 | Check if the files are properly installed in vivo_home cd /opt/vivo/home ; find . | grep fr_CA | OK |