Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-7081

Separate and promote all hippo services modules into standalone projects as needed to prevent dependency build looping

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 2.26.00-alpha-1, 2.26.00
    • None

    Description

      We have to promote the current eventbus and contenttype services, as well as the hippo-services module itself to standalone projects, each with its own version and lifecycle management.

      This is needed to prevent current and future dependency build looping, like as we currently have with the repository being dependent on the eventbus service while the contenttype service is dependent on the repository.

      Attachments

        Activity

          People

            jsheriff Junaidh Kadhar Sheriff
            adouma Ate Douma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: