Uploaded image for project: 'WINDUP - Red Hat Application Migration Toolkit'
  1. WINDUP - Red Hat Application Migration Toolkit
  2. WINDUP-3311

MTA - Strategic solution for repository of known software artifacts

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • MTA CLI
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      * *Why we missed the bug?*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+


       * *What is required:*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+
      Show
      * *Why we missed the bug?*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+  * *What is required:*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+
    • ---
    • ---
    • Priority Backlog, AMM Sprint 223, AMM Sprint 224, AMM Sprint 225, AMM Sprint 228, AMM Sprint 227, AMM Sprint 229, AMM Sprint 230, AMM Sprint 236
    • None

      MTA currently has a Lucene index of sha1 hashes and GAV data for known software artifacts. The source of the data is maven central but the rate that the index is increasing, and it's shear size is bloating the size of the MTA distributions.
      We need a strategic review of how MTA identifies known libraries and the technologies/data structures/processes.

      This Jira is a vehicle for capturing ideas and ultimately implementing the new technical solution.

              Unassigned Unassigned
              pcattana Philip Cattanach
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: