loom
  1. loom
  2. LOOM-52

Build fails due to test failure for ConfigurationMergerTestCase.testAddChild()

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Engine
    • Labels:
      None
    • Number of attachments :
      0

      Description

      I did some debugging and it looks like the problem is the order of child elements in the merged Configuration; I looked into ConfigurationUtil in DNA and it definitely does care what order child Configurations are in.
      To get my version to build I just reversed kid1 and kid2, but we should probably either rethink the merged child order or kick this to DNA. The Configuration comparison is in ConfigurationUtil.equals

        Activity

        Hide
        Peter Donald added a comment -

        Fixed by making sure the order that children are added is the order that they appear in with merged afte base configs

        Show
        Peter Donald added a comment - Fixed by making sure the order that children are added is the order that they appear in with merged afte base configs

          People

          • Assignee:
            Peter Donald
            Reporter:
            Ryan Hoegg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: