DAX API has weird requirements due to properties loading/handling

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • master, 4.0
    • Affects Version/s: master, 4.0
    • Component/s: None
    • None

      We have some properties we want to be required when planning and other tools, but it is now showing up when using the DAX API. For example:

      $ java RosettaDAX dax.xml
      A required property is missing: The pegasus.home.bindir property was not set

      One option is to just not check these properties - but I would like see if we have any other options, maybe changes to the properties loading in the case of using the API.

            Assignee:
            Karan Vahi
            Reporter:
            Mats Rynge [X] (Inactive)
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: