Uploaded image for project: 'VIVO (LEGACY)'
  1. VIVO (LEGACY)
  2. VIVO-1488

Read runtime.properties from {vivo-home}/config

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: v1.9.3
    • Fix Version/s: v1.10
    • Component/s: None
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      5
    • Sprint:
      VIVO Sprint 1

      Description

      After VIVO is built in Maven, example.runtime.properties can be found in {vivo-home}/config. But VIVO expects runtime.properties to be in the top level {vivo-home} and will not start if it is not.  Since runtime.properties is a configuration file, I propose we read it from the config directory. 

      To support users upgrading from previous versions, we can read from both {vivo-home} and {vivo-home}/config. 

      If runtime.properties is found in only {vivo-home}/config, startup as normal. 

      If runtime.properties is found in only {vivo-home}, raise a deprecation warning as part of the smoke tests. User can reload and click continue and VIVO will startup.

      If runtime.properties is found in both {vivo-home}/config and {vivo-home}, raise a deprecation warning with smoke tests and note that the file found in {vivo-home}/config is being used and the file in {vivo-home} is being ignored.

       

       

        Attachments

          Activity

            People

            Assignee:
            mbgross Benjamin Gross
            Reporter:
            mbgross Benjamin Gross
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: