- downloaded binary tarball, checked md5 and sha1 sums
- unpacked, set UIMA_HOME, updated PATH and ran adjustExamplePaths.sh
- ran startBroker.sh to create AMQ broker
- ran basic test (MeetingDetectorTaeQueue) from README
- started oxygen with UIMA_HOME environmental parameter set
- imported uima-a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
signatures OK
build from sources - OK (Windows 10)
compare source-release with svn tag : OK
install into new Eclipse 4.7.0, create deployment descriptor OK
- --- Note: the plugins/features are "unsigned". not a blocker.
issues-fixed: OK
no API cha
starting to work on this
Ping
Need one more vote
Jerry
On Tue, Mar 27, 2018 at 5:10 PM, Burn Lewis wrote:
> - Downloaded binary & source and checked signatures
> - Built from source & checked signatures
> - On both builds ran a couple of UIMA-AS pipelines
> - On both builds verified that multiple JMS service descriptor
- Downloaded binary & source and checked signatures
- Built from source & checked signatures
- On both builds ran a couple of UIMA-AS pipelines
- On both builds verified that multiple JMS service descriptors can connect
to the same service
- Checked README, RELEASE_NOTES,LICENSE and NOTICE
- Spot c
- Built from source - OK
- Spot checked signatures - OK
- issues fixed - OK
- Checked README, RELEASE_NOTES,LICENSE and NOTICE - OK
- Ran runRemoteAsyncAE.sh - OK
- Ran UIMA-AS extended tests which includes a new test which validates
deployment of async aggregate with a delegate which uses Jms Serv