| commit | f212e7c2c3e21d44e90068f9c0bf6ab374a68f8e | [log] [tgz] |
|---|---|---|
| author | Timothy Bish <tabish121@gmail.com> | Tue Jul 23 14:51:37 2019 -0400 |
| committer | Timothy Bish <tabish121@gmail.com> | Tue Jul 23 14:51:37 2019 -0400 |
| tree | 320b18ed3470e83f35a629c98b0a269e0ea024e7 | |
| parent | 45e6ca37b156c34fa25b56b1a10b28234f53842a [diff] |
QPIDJMS-467 Provide client API stack traces in JMS Exceptions Only throw ProviderException types from the provider layer and allow for conversion to the correct JMS exception type in the JMS layer to allow the stack traces in the thrown exceptions to map to which JMS API method was called to trigger the error. Thrown exceptions will provide the cause for the error from the proivider layer from the calling method in the JMS layer.
The QpidJMS project provides a JMS based client that uses the AMQP v1.0 protocol.
Below are some quick pointers you might find useful.
The project requires Maven 3. Some example commands follow.
Clean previous builds output and install all modules to local repository without running the tests:
mvn clean install -DskipTests
Install all modules to the local repository after running all the tests:
mvn clean install
Perform a subset tests on the packaged release artifacts without installing:
mvn clean verify -Dtest=TestNamePattern*
Execute the tests and produce code coverage report:
mvn clean test jacoco:report
First build and install all the modules as detailed above (if running against a source checkout/release, rather than against released binaries) and then consult the README in the qpid-jms-examples module itself.
There is some basic documentation in the qpid-jms-docs module.
After building the modules, src and binary distribution assemblies can be found at:
apache-qpid-jms/target