-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbuild.properties
163 lines (123 loc) · 6.58 KB
/
build.properties
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
#The Grouper UI requires an instance of the Grouper API. This can be a binary distribution
#or a source distribution which has had the 'dist' ant target run.
#If a java/src directory is present the Grouper UI ant html task will create combined
#Javadoc for the UI and the API
grouper.folder=../grouper
#if this is not a grouper source dir, might need to reset some of these
#put the grouper lib dir here
#note, any grouper*.jars here will be ignored.
#e.g. from external: C:/mchyzer/isc/dev/grouper-qs-1.2.0/grouper/lib/grouper
grouper.lib.dir=${grouper.folder}/lib/grouper
#put the grouper jar dir here
#e.g. from external: C:/mchyzer/isc/dev/grouper-qs-1.2.0/grouper/dist/lib/grouper.jar
grouper.jar.name=${grouper.folder}/dist/lib/grouper.jar
#By default the Grouper API log4j.properties file references a System property
#grouper.home. Before building / deploying the UI you should ensure that your
#application server e.g. Tomcat has a System property called grouper.home set*
#or you should replace ${grouper.home} with a valid path. The property below
#will cause ${grouper.home} in log4j.properties to be replaced with the grouper folder
#defined below. This is OK when building and deploying on the same system, however,
#if you are making a WAR file to deploy else where you should not rely on this mechanism.
#* Start your application server with a -Dgrouper.home=<grouper dir>
replace.grouper.home=true
#Must be set to * (any role - including none) or an actual role name (e.g. grouper_user) such that
#HttpServletRequest.isUserInRole(<role_name>) is true for a user to be able to
#log into the UI
grouper.role=*
# Set to false if you want to make manual changes to web.xml or to speed up build
# If you set to false you will need to delete the web.xml to force it to be
# re-built
web.xml.overwrite=true
# Set to true if you want to give users access to lite ui
login.ui-lite.show-link=true
# Set to true if you want the admin-ui to link to the lite ui (membership management only)
ui-lite.link-from-admin-ui=true
#You can override the default browse stem, however, you must ensure that the stem
#exists by creating it using the Grouper API
#default.browse.stem=<stem_name>
# For production turn off (false) or restrict to a group
browser.debug.enable=false
# If debug is on then restrict to named group. Disable if group does not exist
#browser.debug.group=etc:debuggers
# Enables user to specify arbitrary exsecutable as HTML editor on the server
# Do not enable unless you absolutely trust users
browser.debug.group.enable-html-editor=false
#If you want to save your debug preferences, set debug.prefs.dir to an existing directory
#on you system, where the user Tomcat runs as, has write privilege
#debug.prefs.dir=c:/delete
#If you want a unique ticket to be displayed on the error page,set error.ticket=true
#error.ticket=true
#Sets value in media.properties. Note that Grouper cannot guarantee that
#ending the session will log the user out of your authentication system!!!
#Only set to true if you can genuinely logout.
logout.link.show=true
#Switches to UI specific log4j.properties
#use.local.log4j=true
#Make sure directory exists!
#local.log4j.output-dir=c:/tomcat_5-5/logs/
#If you want to email errors append to grouper_mail - only works with use.local.log4j=true
error.append=grouper_log
#error.append=grouper_log,grouper_mail
#Change to valid email addresses
error.mail.to=to@yourhost.edu
error.mail.from=from@yourhost.edu
#Change to a valid smtp server
error.mail.host=smtp.yourhost.edu
error.mail.threshold=ERROR
error.mail.buffer-size=100
error.mail.subject=Grouper UI Error
#uncomment and correct path for subject.folder if you want to generate Subject API
#Javadoc in with Grouper Javadoc
#subject.folder=C:/delete/subject-2005-07-11/subject
#If you are making changes to the API, make sure to uncomment grouper.compile.api=true
#grouper.folder must be set to a source distribution
#grouper.compile.api=true
ui.folder=${basedir}
#Compile UI Java files into temporary folder, JAR and copy to WEB-INF/lib
#Comment out to compile UI Java files direct to WEB-INF/classes
ui.make.jar=true
#Determines the name of the web application
webapp.name=grouper
#Where to build
dist.home=${basedir}/dist
default.webapp.folder=${basedir}/build/${webapp.name}
default.webapp.folder.cleanable=true
#You could insr=tead build in situ - see comments in build.xml
#default.webapp.folder=${basedir}/webapp
#default.webapp.folder.cleanable=false
#add an additonal build file to incorporate site specific changes
#additional.build=${basedir}/../custom-grouper-ui/additional-build.xml
#For development keep these if you want to be able to debug the UI Java source
debug.level=lines,vars,source
########################################################
#You can provide an additional build file which sets 'webapp.folder' so you can build
#to an appropriate location. This provides a way of overriding the 'default.webapp.folder'
#specified above. The build file could present a choice of locations. You must output a file
#called choice.properties and set the property webapp.folder
########################################################
#webapp.choose.build=
##################################################################
#The grouper UI has only been tested with tomcat 4.1x and 5.5. The following properties allow stopping and starting
#of the grouper webapp and determine if and where a grouper.xml (context.xml format) is copied
##################################################################
####Url for Tomcat manager
#deploy.manager.url=http://localhost:8080/manager
####Who to authenticate as
#deploy.manager.username=<local user name>
#deploy.manager.password=<password>
####Web application context - as seen by end user
deploy.context.path=/${webapp.name}
####Root of Tomcat installation
#deploy.home=c:/tomcat_4-1-18
####If you are deploying by war to the webapps dir, then you might consider not having a
####context.xml, it will explode the war with each restart, preventing patching
should.copy.context.xml.to.metainf=true
####Name of context xml file - this will be copied to META-INF and possibly to tomcat webapps directory
####Look at template-tomcat-context.xml for example - you can copy this and adjust
deploy.context.xml=tomcat-context.xml
####Where to copy the context xml - note that the location for Tomcat 5-5 depends on server.xml settings
####Setting this value lets the build script automatically install your webapp on a local Tomcat instance
#deploy.context.dir=c:/tomcat_4-1-18/webapps
#deploy.context.dir=c:/Tomcat_5-5/conf/Catalina/localhost
###If the jdbc drivers should be copied from grouper
copy.grouper.jdbc.sample.drivers=true