@pkornowski, thanks for the update. I respect the decision. Hopefully we can ultimately support older versions over time. One thing we can do now is just keep the possible desire to support older versions in the backs of our minds, particularly when deciding whether to use some feature introduced in Java 8, or another OpenMRS 2.0±only feature that could be done in a more backwards-compatible way.
Just to make sure we are on the same page, I wanted to see if I could get a bit more clarity on some of your points.
This is true. But I would imagine that most of the tests would be shared across versions, and there would need to be more modest additions or changes in version-specific profiles. The reporting module has profiles for 1.9 on up. Still, I agree this is a non-trivial amount of work to support.
Isn’t this already well established across all of the other modules that work between 1.9-2.x? Basically every reference application module supports this, and there are helper classes that are used that does most of the work (eg. DbSessionFactory).
Yes, but as I pointed out in my original post, this is going to continue to happen, and it would be good to know that the module design is robust enough to deal with such changes in the future by ensuring it can handle those that have happened in the past.
I have no idea why the original authors of the FHIR module limited it to OpenMRS 2.1+, but I would have this exact same conversation around that module if I had paid attention. @burke, is there a particular reason why the FHIR module supports 2.1+ only?
Anyway, I don’t say all this to change your opinion necessarily, just to try to get everyone on the same page. Interested in others thoughts on the above…