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 |
|