When Running SW in Quarkus Dev mode, with an Operation to call an OpenAPI, the Quarkus Dev mode always tries to repull the OpenAPI Document and checks/regenerates the OpenAPI Java Classes for each OpenAPI Operation when you make a change to sw.yaml/pom/application.properties.

This means for OpenAPI Documents that are large, the Checks take a long time (30s) before the Quarkus Dev Application is ready and listening.

This leads to unnecessary time and resource used to check/regenerate the OpenAPI class when nothing has changed in the OpenAPI Document. We could achieve better efficiency if we could

• Cache the version of OpenAPI Document last pulled,
• Compare at "Quarkus Dev Recompile", whether the OpenAPI document has been updated relative to Cached version,
• If it has, then regenerate the OpenAPI Classes