Remove trailing whitespace throughout project

This commit is contained in:
gneissone 2019-04-25 14:51:38 -07:00 committed by Andrew Woods
parent 74b8f16aa2
commit bd6140a8cc
1753 changed files with 24077 additions and 24077 deletions

View file

@ -3,7 +3,7 @@
# This file specifies the structure of the Vitro application: which modules
# are used, and what parameters they require.
#
# Most Vitro installations will not need to modify this file.
# Most Vitro installations will not need to modify this file.
#
# For most installations, only the settings in the runtime.properties file will
# be changed.
@ -15,11 +15,11 @@
# ----------------------------
#
# Describe the application by its implementing class and by references to the
# Describe the application by its implementing class and by references to the
# modules it uses.
#
#
:application
:application
a vitroWebapp:application.ApplicationImpl ,
vitroWebapp:modules.Application ;
:hasSearchEngine :instrumentedSearchEngineWrapper ;
@ -32,7 +32,7 @@
# ----------------------------
#
# Image processor module:
# Image processor module:
#
:iioImageProcessor
@ -41,25 +41,25 @@
# ----------------------------
#
# File storage module:
# File storage module:
# The PairTree-inspired implementation is the only standard option.
# It requires no parameters.
#
:ptiFileStorage
:ptiFileStorage
a vitroWebapp:filestorage.impl.FileStorageImplWrapper ,
vitroWebapp:modules.fileStorage.FileStorage .
# ----------------------------
#
# Search engine module:
# Search engine module:
# The Solr-based implementation is the only standard option, but it can be
# wrapped in an "instrumented" wrapper, which provides additional logging
# wrapped in an "instrumented" wrapper, which provides additional logging
# and more rigorous life-cycle checking.
#
:instrumentedSearchEngineWrapper
a vitroWebapp:searchengine.InstrumentedSearchEngineWrapper ,
:instrumentedSearchEngineWrapper
a vitroWebapp:searchengine.InstrumentedSearchEngineWrapper ,
vitroWebapp:modules.searchEngine.SearchEngine ;
:wraps :solrSearchEngine .
@ -69,8 +69,8 @@
# ----------------------------
#
# Search indexer module:
# There is only one standard implementation. You must specify the number of
# Search indexer module:
# There is only one standard implementation. You must specify the number of
# worker threads in the thread pool.
#
@ -78,14 +78,14 @@
a vitroWebapp:searchindex.SearchIndexerImpl ,
vitroWebapp:modules.searchIndexer.SearchIndexer ;
:threadPoolSize "10" .
# ----------------------------
#
# Content triples source module: holds data contents
# The SDB-based implementation is the default option. It reads its parameters
# from the runtime.properties file, for backward compatibility.
#
# Other implementations are based on a local TDB instance, a "standard" SPARQL
# Other implementations are based on a local TDB instance, a "standard" SPARQL
# endpoint, or a Virtuoso endpoint, with parameters as shown.
#
@ -104,7 +104,7 @@
# vitroWebapp:modules.tripleSource.ContentTripleSource ;
# # The URI of the SPARQL endpoint for your triple-store.
# :hasEndpointURI "PUT_YOUR_SPARQL_ENDPOINT_URI_HERE" ;
# # The URI to use for SPARQL UPDATE calls against your triple-store.
# # The URI to use for SPARQL UPDATE calls against your triple-store.
# :hasUpdateEndpointURI "PUT_THE UPDATE_URI_HERE" .
#:virtuosoContentTripleSource
@ -112,7 +112,7 @@
# vitroWebapp:modules.tripleSource.ContentTripleSource ;
# # The URI of Virtuoso's SPARQL endpoint.
# :hasEndpointURI "PUT_YOUR_VIRTUOSO_URI_HERE" ;
# # The URI to use for SPARQL UPDATE calls against Virtuoso.
# # The URI to use for SPARQL UPDATE calls against Virtuoso.
# :hasUpdateEndpointURI "PUT_THE UPDATE_URI_HERE" .
@ -126,10 +126,10 @@
:tdbConfigurationTripleSource
a vitroWebapp:triplesource.impl.tdb.ConfigurationTripleSourceTDB ,
vitroWebapp:modules.tripleSource.ConfigurationTripleSource .
# ----------------------------
#
# TBox reasoner module:
# TBox reasoner module:
# The JFact-based implementation is the only standard option.
# It requires no parameters.
#

View file

@ -3,17 +3,17 @@
#
# Runtime properties for developer mode.
#
# If the developer.properties file is present in the config sub-directory of
# your VIVO home directory, it will be loaded as VIVO starts up, taking effect
# immediately.
# If the developer.properties file is present in the config sub-directory of
# your VIVO home directory, it will be loaded as VIVO starts up, taking effect
# immediately.
#
# Each of these properties can be set or changed while VIVO is running, but it
# Each of these properties can be set or changed while VIVO is running, but it
# can be convenient to set them in advance.
#
# WARNING: Some of these options can seriously degrade performance. They should
# not be enabled in a production instance of VIVO.
#
# For more information go to
# For more information go to
# https://wiki.duraspace.org/display/VIVO/The+Developer+Panel
#
# -----------------------------------------------------------------------------
@ -28,7 +28,7 @@
#------------------------------------------------------------------------------
# Freemarker
# Freemarker
#------------------------------------------------------------------------------
# developer.defeatFreemarkerCache = false
@ -36,7 +36,7 @@
#------------------------------------------------------------------------------
# Page configuration
# Page configuration
#------------------------------------------------------------------------------
# developer.pageContents.logCustomListView = false
@ -44,7 +44,7 @@
#------------------------------------------------------------------------------
# Internationalization
# Internationalization
#------------------------------------------------------------------------------
# developer.i18n.defeatCache = false

View file

@ -4,25 +4,25 @@
#
# This file is provided as example.runtime.properties.
#
# Save a copy of this file as runtime.properties in your Vitro home directory,
# Save a copy of this file as runtime.properties in your Vitro home directory,
# and edit the properties as needed for your installation.
#
# -----------------------------------------------------------------------------
#
# This namespace will be used when generating URIs for objects created in the
# editor. In order to serve linked data, the default namespace must be composed
#
# This namespace will be used when generating URIs for objects created in the
# editor. In order to serve linked data, the default namespace must be composed
# as follows (optional elements in parentheses):
#
# scheme + server_name (+ port) (+ servlet_context) + "/individual/"
#
#
# For example, Cornell's default namespace is:
#
# http://vivo.cornell.edu/individual/
#
Vitro.defaultNamespace = http://vivo.mydomain.edu/individual/
#
#
# URL of Solr context used in local Vitro search. This will usually consist of:
# scheme + server_name + port + vitro_webapp_name + "solr"
# In the standard installation, the Solr context will be on the same server as Vitro,
@ -33,7 +33,7 @@ Vitro.defaultNamespace = http://vivo.mydomain.edu/individual/
vitro.local.solr.url = http://localhost:8080/vitrosolr
#
# Email parameters which VIVO can use to send mail. If these are left empty,
# Email parameters which VIVO can use to send mail. If these are left empty,
# the "Contact Us" form will be disabled and users will not be notified of
# changes to their accounts.
#
@ -41,8 +41,8 @@ email.smtpHost = smtp.my.domain.edu
email.replyTo = vivoAdmin@my.domain.edu
#
# The basic parameters for a MySQL database connection. Change the end of the
# URL to reflect your database name (if it is not "vitro"). Change the username
# The basic parameters for a MySQL database connection. Change the end of the
# URL to reflect your database name (if it is not "vitro"). Change the username
# and password to match the authorized user you created in MySQL.
#
VitroConnection.DataSource.url = jdbc:mysql://localhost/vitro
@ -63,7 +63,7 @@ VitroConnection.DataSource.pool.maxActive = 40
VitroConnection.DataSource.pool.maxIdle = 10
#
# Parameters to change in order to use VIVO with a database other than
# Parameters to change in order to use VIVO with a database other than
# MySQL.
#
VitroConnection.DataSource.dbtype = MySQL
@ -71,8 +71,8 @@ VitroConnection.DataSource.driver = com.mysql.jdbc.Driver
VitroConnection.DataSource.validationQuery = SELECT 1
#
# The email address of the root user for the VIVO application. The password
# for this user is initially set to "rootPassword", but you will be asked to
# The email address of the root user for the VIVO application. The password
# for this user is initially set to "rootPassword", but you will be asked to
# change the password the first time you log in.
#
rootUser.emailAddress = root@myDomain.com
@ -94,7 +94,7 @@ argon2.memory = 1024
argon2.time = 1000
#
# How is a logged-in user associated with a particular Individual? One way is
# How is a logged-in user associated with a particular Individual? One way is
# for the Individual to have a property whose value is the username of the user.
# This is the name of that property.
#
@ -104,11 +104,11 @@ selfEditing.idMatchingProperty = http://vitro.mydomain.edu/ns#networkId
# If an external authentication system like Shibboleth or CUWebAuth is to be
# used, these properties say how the login button should be labeled, and which
# HTTP header will contain the user ID from the authentication system. If such
# as system is not to be used, leave these commented out. Consult the
# installation instructions for more details.
# as system is not to be used, leave these commented out. Consult the
# installation instructions for more details.
#
#externalAuth.buttonText = Log in using BearCat Shibboleth
#externalAuth.netIdHeaderName = remote_userID
#externalAuth.netIdHeaderName = remote_userID
#
# Types of individual for which we can create proxy editors.
@ -116,39 +116,39 @@ selfEditing.idMatchingProperty = http://vitro.mydomain.edu/ns#networkId
proxy.eligibleTypeList = http://www.w3.org/2002/07/owl#Thing
#
# Show only the most appropriate data values based on the Accept-Language
# Show only the most appropriate data values based on the Accept-Language
# header supplied by the browser. Default is false if not set.
#
# RDFService.languageFilter = true
#
# Tell VIVO to generate HTTP headers on its responses to facilitate caching the
# profile pages that it creates.
# Tell VIVO to generate HTTP headers on its responses to facilitate caching the
# profile pages that it creates.
#
# For more information, see
# For more information, see
# https://wiki.duraspace.org/display/VIVO/Use+HTTP+caching+to+improve+performance
#
# Developers will likely want to leave caching disabled, since a change to a
# Freemarker template or to a Java class would not cause the page to be
# Freemarker template or to a Java class would not cause the page to be
# considered stale.
#
# http.createCacheHeaders = true
#
# Force VIVO to use a specific language or Locale instead of those
# specified by the browser. This affects RDF data retrieved from the model,
# Force VIVO to use a specific language or Locale instead of those
# specified by the browser. This affects RDF data retrieved from the model,
# if RDFService.languageFilter is true. This also affects the text of pages
# that have been modified to support multiple languages.
# that have been modified to support multiple languages.
#
# languages.forceLocale = en_US
#
# A list of supported languages or Locales that the user may choose to
# use instead of the one specified by the browser. Selection images must
# be available in the i18n/images directory of the theme. This affects
# RDF data retrieved from the model, if RDFService.languageFilter is true.
# This also affects the text of pages that have been modified to support
# multiple languages.
# be available in the i18n/images directory of the theme. This affects
# RDF data retrieved from the model, if RDFService.languageFilter is true.
# This also affects the text of pages that have been modified to support
# multiple languages.
#
# This should not be used with languages.forceLocale, which will override it.
#