As of VIVO 1.12.0, the build and installation process for the application has changed, as detailed on this page.
Recent versions of VIVO required system administrators or anyone installing VIVO to run a Maven build process, which also copied the exploded "web application archive" (war) into the Tomcat "webapps" directory.
The updated process in 1.12.0 separates the process of building the source code into a "war" file from the process of installation into Tomcat (or Jetty, now!).
One implication of this change is that each release of VIVO will include a deployable "war" file... no building of the software is required to test and/or use VIVO.
Additionally, for those who are used to customizing VIVO with a "custom installer", the same functionality is still available by creating a GitHub fork of vivo-custom-webapp. You can then place your customized code, RDF, property, and template files into your own vivo-custom-webapp. When you build your vivo-custom-webapp, the core VIVO war file is used as a base into which all customizations are included with the Maven overlay process. The resultant war file can then be installed into your servlet container.
Installation Process
Pre-conditions
...
The steps for installing VIVO are:
- Install and configure Solr
- Copy the VIVO war file into your servlet container (Tomcat and Jetty have been tested)
Build Process
To build the VIVO application from source, first clone the source of VIVO and Vitro from GitHub to your local environment.
git clone
