mcsapi added as git submodule and pdi plugin instructed to use libraries from it.

changed version to 1.1.5

tested with a simple insertion on Ubuntu 16.04 and CentOS 7.

This will cause problems with RPM and DEB packaging (if we are going to do that for PDI). Wouldn't a version check be more prudent?

Oh I didn't know about that.

Sure version checking should do the job as well.

We only have to ensure that we can map the shared libraries to the Java libraries.

I am not aware if there is a ldd like function to get the version numbers of the shared libraries for mapping.

Otherwise, hashing would do the job. We could for example store the dependent hashes (of the shared C libraries) in libjavamcsapi.jar's Manifest.

hashes for the shared libraries don't work as the libraries are changed during the installation (Set runtime path...), so we need a different metric for comparison.

Any suggestions?

The C++ API .so file should be versioned in a way that it will create symlinks for its specific version. If you use the full path to the library at link time it will only link with that version. If you don't have that specific version installed it will complain about a missing library at execution time.

• changed mcsapi to include version number as appendix for java libraries
• added symlinks to the base library name for downward compatibility
• changed pdi plugin to use mcsapi's java libraries of version equal to pdi plugin version

— for testing —

• run buildbot (regression suite) to check if mcsapi changes have any unintended impact on any dependent project
• try to build pdi plugin with mcsapi version lower than pdi plugin version (should fail)
• build pdi plugin with mcsapi version equal to pdi version on CentOS 7 and Ubuntu 16.04 and manually run the in repository included test (test/test.kjb) in PDI to verify that the pdi plugin works as expected