Open dotasek opened 1 week ago
There is already a potential solution here: https://github.com/hapifhir/hapi-fhir/pull/6022
From what I can tell, spring-boot-starter-jetty
is picky about the version of jetty, and the versions should align. To see the appropriate jetty version, you can quickly check the dependency listing here (it is jetty 12.0.9) https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-jetty/3.2.6
For comparison, the old version is here: https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-jetty/3.2.0
I'm documenting this issue here in case anyone else runs into an issue when HAPI bumps the version of spring-boot.
When trying to execute the smoke tests in the HAPI release tracking branch (https://github.com/hapifhir/hapi-fhir-jpaserver-starter/pull/684), the running spring-boot using the jetty profile results in an exception and is unable to start the server.
Replication Steps
Run jpaserver-starter using the following command:
mvn -P jetty spring-boot:run
The following exception is thrown, and the server is not available: