[
https://issues.apache.org/jira/browse/TAMAYA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248603#comment-14248603
]
Werner Keil commented on TAMAYA-29:
-----------------------------------
I suppose, if {{Environment}} has enough information about the stage, a
dedicated {{Stage}} class or interface is not really required.
See JSF, its {{ProjectsStage}} enum is insufficient and using a decent string
value instead (even through Java "constants") would have been better.
Looking beyond the Java fence, MultiConf https://github.com/lhupfeldt/multiconf
defines classes like {{Env}}, {{EnvGroup}} or {{EnvFactory}} but no {{Stage}}
either. The stages come into play with examples like
{code}
ef = EnvFactory()
devi = ef.Env('devi')
preprod = ef.Env('preprod')
prod = ef.Env('prod')
{code}
Where the strings are stage ids. Nothing beyond that.
> Remove Stage from the Environment model
> ---------------------------------------
>
> Key: TAMAYA-29
> URL: https://issues.apache.org/jira/browse/TAMAYA-29
> Project: Tamaya
> Issue Type: Task
> Components: Core
> Reporter: Anatole Tresch
> Assignee: Anatole Tresch
>
> Remove Stage from the Environment model, could be modelled within the
> Environment easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
