Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.7.2
-
None
Description
If you try to use different ProjectStages with CdiTestRunner, then only the first one gets used for ConfigResolver.
So this ends up with ProjectStage.Production most of the times.
The reason is that the current ProjectStage gets 'cached' inside ConfigResolver.
We should do some performance tests to check whether we can get rid of that. Because the ProjectStageProducer already uses a cache anyway. So the JIT might level out this method call after a few seconds.