Update pom.xml to reference hapi-fhir 6.3.6-SNAPSHOT. This hapi-fhir release contains a fix for POSTing an XML resource with comments results in a fhir_comments error (#465)

* Update pom.xml to reference hapi-fhir 6.3.4-SNAPSHOT.  This also involves renaming websocket dependencies whose names have changed since 6.2.2 (ex websocket-api to websocket-jetty-api).

* Update pom to reference logback 1.2.10 explicitly to resolve the missing StaticLoggerBinder errors.

* Fix logback issue by pulling the same logback version as hapi-fhir and setting the following system property at boot: org.springframework.boot.logging.LoggingSystem=none.   Also, fix the hapi-fhir-jpaserver-base dependency error by setting this in application.yaml: allow-bean-definition-overriding: true

* Set allow-bean-definition-overriding: true on test application.yaml as well.

* Remove lines in ExampleServerR4BIT that causes an implementation guide version error.

* Upgrade to 6.3.6-SNAPSHOT and once again disable allow-bean-definition-overriding.  Also remove the Bean for IMdmLinkDoa from StartJpaConfig and the Bean for ITermCodeSystemStorageSvc in FhirServerConfigDstu2.

* Explicitly use logback 1.2.10 for both logback-classic and logback-core to resolve StaticBinderLogger not found errors.  Also, remove explici logger disabling code in Application.java.

* Restore Application.java as well as both application.yaml files to the same as master.
This commit is contained in:
Luke deGruchy
2023-01-05 16:56:01 -05:00
committed by GitHub
parent 1943589682
commit 9a513cd184
4 changed files with 16 additions and 22 deletions

View File

@@ -20,8 +20,6 @@ import static org.junit.jupiter.api.Assertions.assertEquals;
"hapi.fhir.fhir_version=r4b",
"hapi.fhir.subscription.websocket_enabled=false",
"hapi.fhir.mdm_enabled=false",
"hapi.fhir.implementationguides.dk-core.name=hl7.fhir.dk.core",
"hapi.fhir.implementationguides.dk-core.version=1.1.0",
// Override is currently required when using MDM as the construction of the MDM
// beans are ambiguous as they are constructed multiple places. This is evident
// when running in a spring boot environment