Andi Huber created ISIS-1991:
--------------------------------
Summary: Determining the deployment type is broken
Key: ISIS-1991
URL: https://issues.apache.org/jira/browse/ISIS-1991
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-M1
Reporter: Andi Huber
Fix For: 2.0.0-M2
We seem to have multiple classes within 'core' that act as advisors for
determining the application's deployment-type.
Maybe we need to rethink and cleanup. I think it should be sufficient to have
one and only one place to configure the deployment type. eg. simply via a
single environment variable.
To pick up this idea [1], we could introduce one layer of abstraction. Also
note: We need to have access to this variable very early in the bootstrapping
phase.
[1]
https://stackoverflow.com/questions/8168884/how-to-test-code-dependent-on-environment-variables-using-junit
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
