Revision 5295
Added by Matt Jones over 14 years ago
build.properties | ||
---|---|---|
11 | 11 |
# build.tomcat.dir=/usr/local/tomcat |
12 | 12 |
build.tomcat.dir=/usr/local/devtools/jakarta-tomcat |
13 | 13 |
|
14 |
# The Maven2 installation directory, for building the dataone-service-api |
|
15 |
# Maven is available here: http://maven.apache.org/ |
|
16 |
maven.home=/opt/local/share/java/maven2 |
|
17 |
|
|
14 | 18 |
# install ant target uses this to determine where to drop |
15 | 19 |
# the war file in an installation. Test classes will use |
16 | 20 |
# this value to find metacat.properties |
... | ... | |
80 | 84 |
# do NOT need to be configured |
81 | 85 |
#metacat.dir=/home/daigle/workspace/metacat |
82 | 86 |
|
87 |
# The location of the dataone source code, defaulting to a directory |
|
88 |
# rooted at a sibling of the current build directory |
|
89 |
d1.dir=../dataone/allsoftware/cicore/service_api |
|
90 |
|
Also available in: Unified diff
Modified the build.xml to include a new task for building the dataone
service api package, which generates a jar file that is put into lib. This
task depends on maven being installed in maven.home, and depends on the
DataONE service_api being checed out in a sibling directory to the build.
If these conditions are not met, then the build skips the dataone build and
instead just uses the checked in service-api jar file.