You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2014/05/03 22:52:15 UTC
[jira] [Updated] (DELTASPIKE-445) read ProjectStage also from a few
other places
[ https://issues.apache.org/jira/browse/DELTASPIKE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek updated DELTASPIKE-445:
----------------------------------------
Fix Version/s: (was: 0.7)
0.8
> read ProjectStage also from a few other places
> ----------------------------------------------
>
> Key: DELTASPIKE-445
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-445
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.8
>
>
> We currently only read the ProjectStage setting from "org.apache.deltaspike.ProjectStage".
> We should also try to read the info from the other ususal suspects:
> - javax.faces.PROJECT_STAGE
> - faces.PROJECT_STAGE
> We have 2 options to do so:
> 1.) introduce a SPI and make it expandable. But I honestly doubt this is worth the hassle.
> 2.) Just add the other locations and iterate through them directly in the ProjectStageProducer.
> I honestly prefer 2. Not as perfectly as clean, but way easier and usually this i snothing a user will change anyway.
--
This message was sent by Atlassian JIRA
(v6.2#6252)