‘ant qa.run’ will run the complete integration test suite. Be warned, though, it takes about 22 hours.
Probably more salient, since this is a “technology preview” release, is to run ‘rat’ against it, and check the licensing. You could also verify the md5, sha and pgp signatures that are on the artifacts. Cheers, Greg Trasuk. > On Mar 2, 2016, at 6:44 PM, Patricia Shanahan <p...@acm.org> wrote: > > I have built from the release artifacts, on a Ubuntu box. What is the > simplest way of running some tests against my build result? > > On 3/2/2016 2:25 PM, Patricia Shanahan wrote: >> I have just got done with another project that was my highest priority >> for a couple of weeks. I'll attempt to build and test so that I can cast >> a binding vote. >> >> On 3/2/2016 12:12 PM, Greg Trasuk wrote: >>> Hi folks - we’re still short one binding vote for this release. So, >>> if you can, please have a look at the artifacts and have your say.. >>> >>> Cheers, >>> >>> Greg Trasuk >>>> On Feb 23, 2016, at 3:43 PM, Greg Trasuk <tras...@stratuscom.com> wrote: >>>> >>>> Hello all: >>>> >>>> Release candidate artifacts can be found at >>>> https://dist.apache.org/repos/dist/dev/river/ >>>> >>>> Binary release artifacts are staged in >>>> https://repository.apache.org/content/repositories/orgapacheriver-1003/ >>>> >>>> The vote will remain open for at least 72 hours (Ending no sooner >>>> than 2100UTC 20160226. >>>> >>>> [ ] +1 : I am in favour of this release >>>> [ ] +0 : I am not opposed to this release. >>>> [ ] -1: I am against this release (please provide your reasons). >>>> >>>> Cheers, >>>> >>>> Greg Trasuk >>>> >>>
