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

Retrieve all Hippo artifacts used as a dependency only through Hippo Nexus

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 2.26.00
    • Fix Version/s: 2.26.00
    • Component/s: channel-manager
    • Labels:
    • Similar issues:
    • Sprint:
      Sprint 76

      Description

      Currently the channel manager frontend module uses Hippo components from github/onehippo directly retrieved (from github) by Bower.
      For a tag or release these dependencies MUST only be retrieved from Hippo Nexus.
      This also means these github/onehippo modules should be released and deployed to Nexus to begin with.
      Preferrably this is also done continuously through a Jenkins Job for current SNAPSHOTs so there will be no need anymore to directly access (download) these from github.
      Finally, to protect against accidentally using such SNAPSHOT dependencies for a tag or release, these dependencies might be first downloaded locally using Maven dependency:copy-dependencies plugin and from there 'downloaded' by Bower. This way, Maven becomes aware again of such dependencies including their possible SNAPSHOT status.

        Attachments

          Activity

            People

            • Assignee:
              jsheriff Junaidh Kadhar Sheriff
              Reporter:
              mdenburger Mathijs den Burger (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: