Deploying fhir module with conditions to ref-application latest

Isn’t this weird?

When running against Core 2.2.x (so that’s within Ref App 2.10.x) you will have a classpath conflict between

  • org.openmrs.Condition coming from Core 2.2.x, and
  • org.openmrs.Condition coming from EMR API.

This is because the api submodule is always depended upon.