You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: test-framework/junit5/src/main/java/io/quarkus/test/junit/AbstractJvmQuarkusTestExtension.java
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -139,8 +139,8 @@ public ConditionEvaluationResult evaluateExecutionCondition(ExtensionContext con
139
139
returnConditionEvaluationResult.enabled("Quarkus Test Profile tags only affect classes");
140
140
}
141
141
142
-
// At this point, the TCCL is usually the FacadeClassLoader, but sometimes it's a deployment classloader (for multimodule tests), or the runtime classloader (for nested tests)
143
-
// Getting back to the FacadeClassLoader is non-trivial. We can't use the singleton on the class, because we will be accessing it from different classloaders.
142
+
// At this point, the TCCL is sometimes a deployment classloader (for multimodule tests), or the runtime classloader (for nested tests), and sometimes a FacadeClassLoader in continuous cases
143
+
// Getting back to a FacadeClassLoader is non-trivial. We can't use the singleton on the class, because we will be accessing it from different classloaders.
144
144
// We can't have a hook back from the runtime classloader to the facade classloader, because
145
145
// when evaluating execution conditions for native tests, the test will have been loaded with the system classloader, not the runtime classloader.
146
146
// The one classloader we can reliably get to when evaluating test execution is the system classloader, so hook our config on that.
0 commit comments