You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltaspike.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2017/05/24 11:53:04 UTC

[jira] [Resolved] (DELTASPIKE-1256) CdiTestRunner ProjectStage setting doesn't work on Config

     [ https://issues.apache.org/jira/browse/DELTASPIKE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved DELTASPIKE-1256.
---------------------------------------
    Resolution: Fixed

> CdiTestRunner ProjectStage setting doesn't work on Config
> ---------------------------------------------------------
>
>                 Key: DELTASPIKE-1256
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1256
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 1.7.2
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.8.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)