diff --git a/doc/install.html b/doc/install.html index c36762fa..00c033cd 100644 --- a/doc/install.html +++ b/doc/install.html @@ -60,7 +60,7 @@
When you run the build script to compile and deploy VIVO
- (see Step 6, below), the files will be deployed to a
+ (see Step 5, below), the files will be deployed to a
directory inside Tomcat. This is the actual executing code for VIVO,
but you won’t need to look at it or change it. If you need to change
VIVO, make the changes in the distribution directory, and run the build
@@ -78,7 +78,7 @@
in the build.properties file (see Step 4,
below). You must create this directory before starting VIVO,
you must create the runtime.properties
file in this directory
- (see Step 5, below), and you
+ (see Step 6, below), and you
must ensure that Tomcat has permission to read and write to this
directory when it runs.
These properties are used in compilation and deployment. They will be incorporated into VIVO when it is compiled in - Step 6. If you want to change these properties at - a later date, you will need to stop Tomcat, repeat Step 6, + Step 5. If you want to change these properties at + a later date, you will need to stop Tomcat, repeat Step 5, and restart Tomcat.
@@ -343,22 +342,62 @@ issuing SPARQL queries that read data, and its URI for issuing SPARQL UPDATE com -
In Step 4, you defined the location of the VIVO home directory,
by specifying vitro.home
in the build.properties
file.
Create that directory now.
- At the top level of the VIVO distribution directory, you will find a file called
- example.runtime.properties
. Copy this to the VIVO home directory you have created,
- renaming the copy to runtime.properties
.
- Edit the file to suit your installation, as described in the following table.
+ At the command line, from the top level of the VIVO distribution
+ directory, type:
+
ant all+ to build VIVO and deploy to Tomcat's webapps directory. + +
+ The build script may run for as much as five minutes, + and creates more than 100 lines of output. + The process comprises several steps: +
+ The output of the build may include a variety of warning messages. + The Java compiler may warn of code that is outdated. + Unit tests may produce warning messages, + and some tests may be ignored if they do not produce consistent results. +
+
+ BUILD SUCCESSFUL Total time: 1 minute 49 seconds + |
+ If the output ends with a success message, the build was successful. + Proceed to the next step. +
+
+ BUILD FAILED Total time: 35 seconds + |
+ If the output ends with a failure message, the build has failed. + Find the cause of the failure, fix the problem, and run the script again. +
+ +
+ The build process in Step 5 created a file called example.runtime.properties
+ in your VIVO home directory (vitro.home
in the build.properties
file).
+ Rename this file to runtime.properties
, and
+ edit the file to suit your installation, as described in the following table.
These properties are loaded when VIVO starts up. If you want to change these properties at a later date, you will need to restart Tomcat for them to take - effect. You will not need to repeat Step 6. + effect. You will not need to repeat Step 5.
Windows: @@ -921,45 +960,6 @@ issuing SPARQL queries that read data, and its URI for issuing SPARQL UPDATE com -
- At the command line, from the top level of the VIVO distribution - directory, type: -
ant all- to build VIVO and deploy to Tomcat's webapps directory. - -
- The build script may run for as much as five minutes, - and creates more than 100 lines of output. - The process comprises several steps: -
- The output of the build may include a variety of warning messages. - The Java compiler may warn of code that is outdated. - Unit tests may produce warning messages, - and some tests may be ignored if they do not produce consistent results. -
-
- BUILD SUCCESSFUL Total time: 1 minute 49 seconds - |
- If the output ends with a success message, the build was successful. - Proceed to the next step. -
-
- BUILD FAILED Total time: 35 seconds - |
- If the output ends with a failure message, the build has failed. - Find the cause of the failure, fix the problem, and run the script again. -
continue
link which
will allow you to use VIVO in spite of the problems.
diff --git a/doc/upgrade-1.6.html b/doc/upgrade-1.6.html index 3b7b9b58..42bc64d5 100644 --- a/doc/upgrade-1.6.html +++ b/doc/upgrade-1.6.html @@ -436,24 +436,26 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl
For this release, the following browsers are supported.
-- Mac: -
-
+
diff --git a/rdf/display/everytime/PropertyConfig.n3 b/rdf/display/everytime/PropertyConfig.n3
index 7f2b7bd0..0ae8434d 100644
--- a/rdf/display/everytime/PropertyConfig.n3
+++ b/rdf/display/everytime/PropertyConfig.n3
@@ -27,6 +27,7 @@ local:personInPositionConfig a :ObjectPropertyDisplayConfig ;
:propertyGroup