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

MTA 5.2.1.Final - Update developers website

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • MTA CLI
    • None
    • False
    • 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:_+
    • ---
    • ---
    • Sprint 211 AMM, Sprint 212 AMM
    • None

      Make sure all of the links for the docs are pointing to the 5.2 versions.

      We definitely need to add a link to the VSCode Extension Guide  https://access.redhat.com/documentation/en-us/migration_toolkit_for_applications/5.2/html/visual_studio_code_extension_guide 

      We might want to consider adding some additional content on the Use Cases page to show that we cater for Jakarta EE 9 - link

      I think a Jakarta EE 9 column to the left of Camel 3 with a tick for the Any Java application row.

      We should add some text in bold on both the Overview and Downloads page immediately below the tabs

      MTA does not depend on Log4j 2 so we are not affected by CVE-2021-44228.

      Is the caveat about EAP XP2 still appropriate?

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

                Created:
                Updated:
                Resolved: