- reverted mysql as default and used derby based on change request 6858c0d799 (r266028296) and updated readme to include specifics on configuring mysql
- defaulted to jetty configs on hapi.properties so that this starter app will outright work without changing any configs with mvn jetty:run
- updated subscription configs as it doesn't match already active subscription on subsequent runs using mysql as db
- updated project based path resolution and removed unused file .keep_hapi-fhir-jpaserver-starter
- updated fhir version to R4 and used mysql as datasource with docs updated
- transferred jetty plugin to be viewable on intellij
- disabled oss snapshots
- replaced corsFilter based on new hapi docs
Such configurations can be specified in a properteis file outside of the war (or
webapps/hapi-fhir-jpaserver) and the server may be instructed to load the configuration using
-Dhapi.properties=<path-of-external-configuration-file>
This is helpful in at least two use cases:
1. Deploying multiple instances with different configurations (e.g., differnt databases)
2. Future upgrade - just update the war without the need to change hapi.properties after update.
