From 6eb1332fcded57e8e45043adfec3f8f28a170346 Mon Sep 17 00:00:00 2001 From: Georgios Andrianakis Date: Mon, 1 Mar 2021 15:03:07 +0200 Subject: [PATCH] Bring back proper timing for quarkus:dev This seems to have been (erroneously) removed in 3a6b561c35f66ffe6d4fdfacac5ca2780aea8bb3 Fixes: #15371 --- .../main/java/io/quarkus/deployment/dev/IsolatedDevModeMain.java | 1 + 1 file changed, 1 insertion(+) diff --git a/core/deployment/src/main/java/io/quarkus/deployment/dev/IsolatedDevModeMain.java b/core/deployment/src/main/java/io/quarkus/deployment/dev/IsolatedDevModeMain.java index ee2baa7a20b841..6dc5207d5fa9d8 100644 --- a/core/deployment/src/main/java/io/quarkus/deployment/dev/IsolatedDevModeMain.java +++ b/core/deployment/src/main/java/io/quarkus/deployment/dev/IsolatedDevModeMain.java @@ -297,6 +297,7 @@ public void close() { //the main entry point, but loaded inside the augmentation class loader @Override public void accept(CuratedApplication o, Map params) { + Timing.staticInitStarted(o.getBaseRuntimeClassLoader()); //https://github.com/quarkusio/quarkus/issues/9748 //if you have an app with all daemon threads then the app thread //may be the only thread keeping the JVM alive