Alfiva
commented
4 years ago I have been testing a bit and it's more complicated than just increasing the version. It seems rdf4j 3.x uses java 1.8, which would break our current compatiblity with 1.5. With version 2.x, the latest one is 2.5.5, which adds some extra dependencies to those we already have (like commons lang3) which we curently don't include anywhere. If the goal is to get our custom runtime-osgi rdf4j bundle runnign in the latest OpenHAB, there are 2 alternative solutions:
- Use rdf4j 2.5.5 and make the new dependencies optional so they are ignored (but I don't know it that will affect the used code)
- Keep using rdf4j 2.3.1 (the one we use now) but specify it to use apache.commons version 2.2.0 in the custom bundle imports.
I don't think we should move to 3.x, given the Java 1.8 requirement. At least not for now. Perhaps for uAAL 4.0.0.
After checking LDDI OpenHab exporter, I have seen that CHe dependency rdf4j is not compatible with latest version of OpenHAB because of not using updated versions of Apache commons. Basically, we need to update rdf4j dependencies, which have gone from 2.x to 3.x. This requires checking that the version bump does not interfere with our current usage, and then update the custom runtime-osgi bundle where we pack all rdf4j libs we need.