...
In order to manage the state of VIVO home directory a digest.md5 file has been introduced. It will afford maintaining customizations through restarts and upgrades. The implementation can be found in VitroHomeDirectory.java.
On first startup
- packed vivo VIVO home tar file is untarred into vivo home
- if file already exists it will be overwritten*
- digest.md5 file is created of a checksum per tar entry
...
- digest.md5 is read in to determine if any files have changed
- packed vivo VIVO home tar file is untarred
- if file already exists and matches digest checksum and does not match tar entry checksum, file is overwritten
- digest.md5 file is created of a checksum per tar entry
...
This will produce a VIVO war file in the "installer/webapp/target/" directory, named with the default application name: vivo.war
| Note |
|---|
The build process also creates an intermediate war file in the "webapp/target" directory. This war file does not contain the complete VIVO application and will not run if copied into Tomcat's webapps directory. Be sure that you use only the war in "installer/webapp/target". |
If you do not specify the "vivo-dir" location as a build parameter, you must provide the "vivo-dir" location with one of the other two detailed in the "VIVO Home Directory" section above.
...