Hey, I ran into a weird issue today. I have two tests based on Arquillian, and both have some DeltaSpike dependencies in them.
The test I'm running is against Weld EE embedded, it's not spawning new JVMs or anything, but each test has its own deployment. The weird part about the two deployments is that they had different class deactivators. I ran into an issue in that TestA ran before TestB. During TestB's execution, I was seeing deacitvation behavior based on the configuration of TestA. I realized much later that the cause is that the class deactivation result is computed and cached, which is fine for production code but for unit tests I would hope that it behaves more idempotent. https://github.com/apache/deltaspike/blob/master/deltaspike/core/api/src/main/java/org/apache/deltaspike/core/util/ClassDeactivationUtils.java#L47 I'm wondering if it's possible to expose a method to allow devs to reset the deacitvation cache between test runs. WDYT? John
