[CAUSEWAY-1991] Determining the deployment type is broken

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Resolved
• Affects Version/s: 2.0.0-M1
• Fix Version/s: 2.0.0-M2
• Component/s: Core
• Assignee: Andi Huber
• Reporter: Andi Huber
• Created: 24/Sep/18 16:03
• Updated: 18/Nov/18 18:04
• Resolved: 18/Nov/18 09:36

Description

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

Issue Links

• causes: CAUSEWAY-2036 When PROTOTYPING prototyping toplevel menu is (sometimes?) hidden
• contains: CAUSEWAY-890 Get rid of exploration mode, treat as synonym for prototype. Ditto with @Exploration annotation.