Uploaded image for project: 'Causeway'
  1. Causeway
  2. CAUSEWAY-1991

Determining the deployment type is broken

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Resolved
    • 2.0.0-M1
    • 2.0.0-M2
    • Core
    • None

    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

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. CAUSEWAY-2036 When PROTOTYPING prototyping toplevel menu is (sometimes?) hidden

          • Major - Major loss of function.
          • Closed
          contains

          Improvement - An improvement or enhancement to an existing feature or task. CAUSEWAY-890 Get rid of exploration mode, treat as synonym for prototype. Ditto with @Exploration annotation.

          • Major - Major loss of function.
          • Closed

          Activity

            People

              hobrom Andi Huber
              hobrom Andi Huber
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: