j2blake
153cd6f117
VIVO-773 create the RDB to TDB migration utility.
2014-06-11 12:07:05 -04:00
j2blake
9e2519af21
VIVO-725 modify TestLinkedOpenData so it can be fully automated.
2014-03-26 16:06:29 -04:00
j2blake
805491e52f
In the build, apply “skipinfo” consistently.
2013-11-14 11:14:32 -05:00
j2blake
e3227af798
VIVO-262 Add languages to VIVO at build time.
...
Move the language-specific files out of the default build area. Add a build property that will cause the selected language(s) to be copied into the build area.
2013-09-09 12:23:36 -04:00
j2blake
5f7bbc6799
VIVO-248 Use /rdf instead of /rdffiles
2013-08-21 15:55:07 -04:00
j2blake
ca951c6bf3
VIVO-248 Move filegraph RDF files into the home directory
2013-08-20 15:26:09 -04:00
j2blake
89f759fcbc
VIVO-2 Modify the build so installers can create a container-neutral VIVO.
...
Split deploy.properties into build.properties and runtime.properties, with runtime.properties going into the Vitro home directory. Modify ConfigurationProperties to locate the Vitro home directory, either by System property or JNDI Environment variable, or from build.properties, and to read from both build.properties and runtime.properties. Revise the install and upgrade documents for VIVO and Vitro. Change comments and error messages that referred to deploy.properties by name.
2013-01-16 14:52:35 -05:00
j2blake
ebfefce352
NIHVIVO-3597 Use a <FileSet> with a <present> selector instead of the home-brewed DirDifferenceFileSet
2012-03-02 21:22:25 +00:00
j2blake
a95ee35048
NIHVIVO-2774 improve the "jarlist" target in the build so known required JARs are listed in a file, and not hardcoded.
2011-10-19 20:47:01 +00:00
j2blake
e5723abab2
Fix a comment.
2011-10-12 21:07:06 +00:00
j2blake
4b59676c45
Make sure that the new startup_listeners.txt file gets into the new build.
2011-09-20 19:35:03 +00:00
j2blake
66252c17f1
NIHVIVO-2811 remove product-build.xml, since the code is now small enough and ideosyncratic enough to go into VIVO and VivoCornell's build files.
2011-09-12 20:39:44 +00:00
j2blake
9fcac79e34
NIHVIVO-2811 Rewrite the build for vivoCornell; minor tweaks for the others.
2011-09-12 16:55:35 +00:00
jeb228
fc6da3a68f
Modify the build script to allow multi-layer products.
2010-08-03 18:54:07 +00:00
jeb228
a2595050b4
NIHVIVO-239 Set up to run acceptance tests from Vivo.
2010-06-03 19:01:27 +00:00
jeb228
5b77126d36
NIHVIVO-241 Move the licenser script into Vitro core, with some re-writing to use relative paths and such, and changes to the build scripts to support it.
2010-04-15 20:20:35 +00:00
jeb228
4f6090003f
NIHVIVO-324 merge revision 397 into trunk
2010-04-08 18:51:09 +00:00
jeb228
2417058a4f
NIHVIVO-46 Fix spelling error
2010-03-24 20:06:48 +00:00
jeb228
2763ad9e64
NIHVIVO-46 Create an Ant task to run the licenser.
2010-03-24 19:42:38 +00:00
jeb228
5520c5be0a
NIHVIVO-76 In the build, break the acceptance tests into 2 steps: running and collating. And between the steps, fail if we find the word Error or Exception in the output from selenium/ruby.
2010-03-16 21:37:41 +00:00
jeb228
31ebff72fd
NIHVIVO-76 Take out the intentional failure in the acceptance tests.
2010-03-16 20:59:13 +00:00
jeb228
c790aa60ea
NIHVIVO-76 Break the acceptance tests, to see how Hudson reacts.
2010-03-16 20:27:40 +00:00
jeb228
854f256a05
NIHVIVO-76 Tweak the build script to give up on the ant-ruby-output.
2010-03-15 21:45:21 +00:00
jeb228
0955a1f010
NIHVIVO-76 Tweak the build script so we can write the ant-ruby-output to the output directory.
2010-03-15 21:41:31 +00:00
jeb228
310f3d484d
NIHVIVO-76 Create an "acceptance" target in the build script, and an output directory in the acceptance-tests folder.
2010-03-15 20:22:16 +00:00
jeb228
f85da80bb7
NIHVIVO-56 Correct spelling error (RATS)
2010-02-21 20:43:33 +00:00
jeb228
710ddfedc6
NIHVIVO-56 Adjust to the restructured core build script - use a build that is based on the core product-build script.
2010-02-21 18:46:05 +00:00
jeb228
fcba81c3a4
NIHVIVO-15 Adjust to the changes in the Vitro configuration properties files.
2010-02-03 15:10:24 +00:00
jeb228
3f17d16d7b
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.
2010-01-29 22:12:41 +00:00