Rafael Schloming-3 wrote > These projects aren't actually quite as independent as they look. There is > a common test suite that runs against both implementations to help keep > them in sync with each other. This is the python test suite that lives > underneath the top level tests/python directory. > These tests have been integrated into the maven build via jython so that > the whole java build looks like a normal maven build and java developers > don't need to deal with cmake or getting jython themselves or anything > that's outside of the normal java experience. > > Likewise, the cmake build will detect if java is unavailable and opt out > of > building the java code, so it's easy for C developers to pretend that Java > doesn't exist. It also does this for all the different bindings, e.g. if > perl or ruby isn't installed it will not attempt to build them.
This quoted part of the explanation is a little confusing in the context of the rest of it. It seems that it should be (and already is) a continuous-integration requirement that the common test suite (python+proton-c and jython+proton-j) passes across the whole repository before code can be delivered/committed. But unless you change the defaults so that they enforce that both proton-c and proton-j are built and the full suite is run by default on all entry points (either maven or cmake) then breaking changes are more likely to slip through the cracks. -- View this message in context: http://qpid.2158936.n2.nabble.com/proton-j-proton-c-integration-primer-tp7619387p7619410.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
