Versions Compared

Old Version 1

changes.mady.by.user Dragan Ivanovic

Saved on

compared with

New Version Current

changes.mady.by.user Dragan Ivanovic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagetext
vivo-1.1314.0/
  pom.xml
  example-settings.xml
  home/
    pom.xml
    src
  webapp/
    pom.xml
    src

...

  • The maven user has write permission to the Tomcat webapps directory. Maven will fail silently if it cannot copy files to tomcat.
  • The tomcat user has write permission to the <vivo-dir>/home  directory. Please note there might be some specificity for tomcat read/write permissions depending on operating system and tomcat version, such as Tomcat 9 (Debian). 

Installing VIVO

Once you have an appropriate settings file (these instructions will assume that you are using example-settings.xml - replace this with your actual file), you simply need to run Maven, specifying the install goal and your settings file.

...

In order to install the development code from GitHub, you need to clone both the Vitro and VIVO repositories from the vivo-project organization. These clones should be in sibling directories called "Vitro" and "VIVO" respectively.  These will all point to the 1.1314.1-SNAPSHOT:

Code Block
languagetext
$ git clone https://github.com/vivo-project/Vitro.git Vitro -b rel-1.13.014-maint
$ git clone https://github.com/vivo-project/VIVO.git VIVO -b rel-1.13.014-maint
$ git clone https://github.com/vivo-project/Vitro-languages.git Vitro-languages -b rel-1.13.0-maint  
$ git clone https://github.com/vivo-project/VIVO-languages.git VIVO-languages -b rel-1.13.0-maint 
drwxr-xr-x  user  group  1 Dec 12:00drwxr-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.

...