Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-639

Unify and Simplify the various .conf handling

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2016.9
    • Component/s: None
    • Labels:
      None

      Description

      Currently we have a variety of random .conf files within fractions and within packaged applications which sometimes produce confusing or duplicitous information.

      Also, we have several places within the codebase that reads/handles those files.

      In order to de-intertwingly the swarm and application dependencies, it'd be much happier to have a single file (probably .yaml) that manages all of the meta-data for each fraction and likewise a single file (also probbaly .yaml) that manages all the meta-data for the packaged application.

      All of this should be unified into a single view of the running application, instead of a variety of classes making choices about uberjar/classpath/ide execution models.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bob.mcwhirter Bob McWhirter
                  Reporter:
                  bob.mcwhirter Bob McWhirter
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: