Comparaison des versions

Ancienne version 2

changes.mady.by.user Héon, Michel

Sauvegardée le

comparé à

Nouvelle version Actuel

changes.mady.by.user Héon, Michel

Sauvegardée le

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.

...

In this scenario. the packages of (VIVO and Vitro) languages are previously compiled before the execution of Maven in the directory VIVO/installer


ActionDescription
1Installing Vitro-languages
cd ~/TEST-VIVO/Vitro-languages 
mvn clean install

Image Modified

(This step generates a lot of download of Maven -Central because of the (~/.m2) directory cleaning )

2Installing Vivo-languages
cd ~/TEST-VIVO/VIVO-languages
mvn clean install


As you can see the packages are installed in the subdirectory (1.11.2-SNAPSHOT) of Maven (~/.m2)

Image Modified

3Installing VIVO
cd ~/TEST-VIVO/VIVO/installer/
mvn -s settings.xml clean install

Image Modified

Observations:

All comments come from the analysis of the log file captured during the installation of VIVO (Pojnt 3)

View file
namevivo_install.log
height150


Action
Description
ResultComments
1

grep -i SNAPSHOT vivo_install.log

Filter on SNAPSHOT to evaluate the processed version

Image Added

  • The release is at 1.11.2 instead of 1.12.0-RC
  • The log indicates that the associated files (VIVO/Vitro)-(home-webapp-api) are downloaded rather than compiled
2

Check if the files are properly installed in tomcat

cd /opt/tomcat/webapps/ ; find . | grep fr_CA

Image Added

OK
3

Check if the files are properly installed in vivo_home

cd /opt/vivo/home ; find . | grep fr_CA

Image Added

OK
123