Tweak the build script, so a developer can build vitro-core and it won't have any effect when they build vivoweb in the same workspace.

This commit is contained in:
jeb228 2010-01-29 22:12:41 +00:00
commit 3f17d16d7b
68 changed files with 40148 additions and 0 deletions

View file

@ -0,0 +1,11 @@
#this is an example of what needs to be in this
#file to setup the lucene index directory
#
# The default location is /usr/local/lucene/vitrodefault
#You could hard code the location like this:
#LuceneSetup.indexDir=/usr/local/lucene/example
#this line will be setup by ant to work for clones
#if you hardcode the dir, this line should be commented out
LuceneSetup.indexDir=${deploy.LuceneSetup.indexDir}

58
config/build.properties Normal file
View file

@ -0,0 +1,58 @@
#
# This is where we're assembling the source.
#
deploy.staging.dir = .deployStaging
#
# Setting up the config properties.
#
deploy.properties.file = deploy.properties
globalbuild.template.file = config/globalbuild.properties.template
connection.template.file = config/connection.properties.template
upload.template.file = config/upload.properties.template
lucene.template.file = config/LuceneSetup.properties.template
vitroUsers.template.file = config/vitroUsers.owl.template
globalbuild.properties.file = ${deploy.staging.dir}/config/globalbuild.properties
connection.properties.file = ${deploy.staging.dir}/webapp/config/connection.properties
upload.properties.file = ${deploy.staging.dir}/webapp/config/upload.properties
lucene.properties.file = ${deploy.staging.dir}/webapp/config/LuceneSetup.properties
vitroUsers.owl.file = ${deploy.staging.dir}/webapp/ontologies/auth/vitroUsers.owl
#
# Prepare the staging area
#
core-build.blocking.path = webapp/.build/**/*
themes.blocking.path = webapp/web/themes/**/*
#
# Installing the themes.
#
themes.source.dir = themes/
themes.destination.dir = ${deploy.staging.dir}/webapp/web/themes/
#
# Installing the Ontology.
#
ontology.source.dir = ontology
ontology.destination.dir = ${deploy.staging.dir}/webapp/ontologies/user
#
# Installing the Model.
#
submodels.source.dir = model/submodels
submodels.destination.dir = ${deploy.staging.dir}/webapp/model/submodels
init-data.source.dir = model/init-data
init-data.destination.dir = ${deploy.staging.dir}/webapp/model/init-data
#
# Adding modifications
#
modifications.source.dir = modifications
modifications.destination.dir = ${deploy.staging.dir}/webapp/web
#
# The core compile and deploy.
#
vitro-core.build.file = ${deploy.staging.dir}/webapp/build.xml

View file

@ -0,0 +1,80 @@
################################################################################
# DataSource properties file
################################################################################
######################### DataSource Properties ################################
VitroConnection.DataSource.url=${deploy.VitroConnection.DataSource.url}
VitroConnection.DataSource.username=${deploy.VitroConnection.DataSource.username}
VitroConnection.DataSource.password=${deploy.VitroConnection.DataSource.password}
####################### Other Important Properties #############################
# CHANGE the following property unless you're using Cornell's VIVO ontology
Vitro.defaultNamespace=${deploy.Vitro.defaultNamespace}
# Uncomment this next line and specify an SMTP host to activate the Contact Us form
#Vitro.smtpHost=
################################################################################
# maximum number of connections to the db server
# This must not be greater than the mysql max_connection parameter.
# defaults to 40
#VitroConnection.DataSource.MaxActive=40
# maximum number of connections to the db server to keep
# around when nothing is happening.
# defaults to 10
#VitroConnection.DataSource.MaxIdle=10
# Time to wait in msec for a result from the sql server
# defaults to 10000
#VitroConnection.DataSource.MaxWait=10000
# query to use to test to see if a connection to the db server is live.
# defaults to SELECT 1
#VitroConnection.DataSource.ValidationQuery=SELECT 1
# should the connection pool test the connections it gets from the pool?
#defaults to true
#VitroConnection.DataSource.TestOnBorrow=true
# should the connection pool test connections it puts back in pool?
#defaults to true
#VitroConnection.DataSource.TestOnReturn=true
# Nnumber of milliseconds to sleep between runs of the idle object
# evictor thread. When non-positive, no idle object evictor thread will
# be run. defaults to 30min
#VitroConnection.DataSource.TimeBetweenEvictions=
# The number of objects to examine during each
# run of the idle object evictor thread (if any).
# defaults to 3
#VitroConnection.DataSource.TestsPerEviction=3
# The minimum amount of time
# an object may sit idle in the pool before it is eligable for eviction
# by the idle object evictor (if any).
# defaults to 30min
#VitroConnection.DataSource.MinEvictionIdleTime=
################################################ # other notes:
# The file checked into source control is example.connection.properties so
# that if you have a connection.properties on your machine it will not be
# under source control. This is useful so that your customizations for your
# database setup are less likely to be checked into source control and then
# overwrite other folks' customizations.

View file

@ -0,0 +1,49 @@
# these are ant build properties that all of the vitro and build.xml files might need.
#
# All of these paths must be absolute or relative to the vitro directory. Relative
# is preferred.
# Notice that the use of relative paths is facilitated by the basedir attribute of the
# ant project elements. All projects should use the same base directory so that the
# relative paths will point to the correct files.
# See the ant documentation for project element basedir attribute.
############## basic configuration ###############
java_api=/usr/local/java/java_home
############ tomcat stuff ####################
tomcat.home=${deploy.tomcat.home}
############# source directory #########################################
##### This parameter is used for referencing a "permanent" home #######
##### in the source directory of the project for uploaded files #######
##### so that if the Tomcat webapp context is wiped out, any #######
##### uploaded files (usually images) are not lost. #######
########################################################################
source.home=/usr/local/src/Vitro
########################################################################
##### Everything under this is used by the Vitro build.xml files #######
##### You should not need to customize it for you local install #######
########################################################################
########### ant contrib tasks ###############
ant.lib=./config/ant/lib
ant.contrib.jar=${ant.lib}/ant-contrib-1.0b2.jar
#### locations of files in the build #####
webapp.dir=./webapp
webapp.lib=${webapp.dir}/lib
webapp.build=${webapp.dir}/.build
webapp.dir.jar=${webapp.build}/vitro-webapp.jar
webapp.name=${deploy.webapp.name}
webapp.deploy.home=${tomcat.home}/webapps/${webapp.name}
ingest.dir=./ingestTool
ingest.lib=${ingest.dir}/lib
ingest.build=${ingest.dir}/build
ws.dir=./services
ws.lib=${ws.dir}/lib
ws.build=${webapp.dir}/build
ws.wsdd.dir=${ws.dir}/wsdd

View file

@ -0,0 +1,26 @@
# The UploadImagesServlet will upload the images to a directory
# that is under tomcat and serve them from there.
# This causes a problem when the tomcat/webapps dir is deleted
# or deployed because you will lose all the images that the
# curators have uploaded. We deal with this by copying
# the files to another directory, one that is under version control.
# This property indicates which non-tomcat directory to save the images in.
# ${uploadDir} is defined in the main build.xml via the following statements:
#
# <!-- defined in globalbuild.properties -->
# <property name="source.dir" value="{source.home}"/>
# <property name="uploadDir" value="{source.dir}/webapp/web" />
#
# But, this value will be replaced by the Vitro/clones/build.xml
# to point to the clones/{clone}/modifications directory based on the following
# <property file="./config/globalbuild.properties"/>
# <property name="source.dir" value="{source.home}"/>
# <property name="uploadDir" value="${source.dir}/clones/${clone}/modifications"/>
#
# The UploadImagesServlet.getSourceDirName() method then looks at this parameter
# in the upload.properties file, which file is stuck by the clones/build.xml file
# into the clone's modifications/WEB-INF/classes directory:
UploadImagesServlet.sourceDirName=${deploy.upload.directory}

View file

@ -0,0 +1,15 @@
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:vitro="http://vitro.mannlib.cornell.edu/ns/vitro/0.7#"
xmlns="http://vitro.mannlib.cornell.edu/ns/vitro/default#"
xml:base="http://vitro.mannlib.cornell.edu/ns/vitro/default">
<vitro:User rdf:about="#defaultAdminUser">
<vitro:username rdf:datatype="http://www.w3.org/2001/XMLSchema#string">${deploy.initialAdminUser}</vitro:username>
<vitro:md5password rdf:datatype="http://www.w3.org/2001/XMLSchema#string">22BA075EC8951A70960A0A95C0BC2294</vitro:md5password>
<vitro:roleURI rdf:datatype="http://www.w3.org/2001/XMLSchema#string">role:/50</vitro:roleURI>
</vitro:User>
</rdf:RDF>