The changes on the jni-branch are nearing completion. The changes with respect to current trunk are summarised below.
README/LICENCE files have been moved to the proton level. The README has been updated to reflect the new practice.
Build is now performed from the parent (proton) directory rather than proton-c.
If Cmake can find the JDK, proton-api and proton-jni will be built, otherwise they are skipped
If Cmake can find** Bouncycastle JARs, proton-j-impl will be built, otherwise it is skipped.
- JAR search path is defined by Cmake's find_jar() function as /usr/share/java/ and /usr/local/share/java/. This can be supplemented on the command line via:
cmake -DPROTON_JAR_DEPEND_DIR=... ..
Testing Proton-C (Python tests)
proton-test script and the Python tests have moved to accommodate tests written in other languages.
Build is now performed from the parent (proton) directory rather than proton-j.
Typical maven commands:
mvn compile -DskipTests # compile everything, skipping the tests
mvn package # package everything
Testing Proton-J/Proton-C via JNI bindings
mvn test -Pproton-j # Run all system tests against proton-j
mvn test -Pproton-jnj # Run all system tests against proton-c using jni wrappers ***
mvn test -Pproton-j -Dproton.pythontest.pattern='proton_tests.transport.TransportTest.*' # Run Python tests matching patterm
- you need to have previously built proton-c with the JNI bindings.