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

MTR/MTA IDE extension compatibility with the new PF4 based Reports

    XMLWordPrintable

Details

    • False
    • 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:_+
    • No
    • ---
    • ---
    • AMM Sprint 233, AMM Sprint 234, AMM Sprint 235, AMM Sprint 236, AMM Sprint 237, AMM Sprint 238, AMM Sprint 239, AMM Sprint 240

    Description

      Related to WINDUP-3561 new PF4 Reports

      The changes introduced to the CLI under PRs below generate a CLI that produces the new format reports.

      https://github.com/windup/windup/pull/1579
      https://github.com/windup/windup-rulesets/pull/900
      https://github.com/windup/windup-distribution/pull/101

      This version needs to be included in MTR 1.1.0
      We need to ensure that the new PF4 Reports are compatible with the existing IDE Plugins
      If it is helpful we can create a sub-task for Eclipse, IntelliJ , VSCode / Eclipse Che

      The attached shows an issue and the new Source Code Report.
      It is also worth noting that the old reports can be still generated via the --legacyReports advanced option.
      I wouldn't expect the IDEs to have to provide that legacy option. As I'd only want the IDEs to have to manage one format of output.

      When the PRs for the new Reports are merged we could add the --legacyReports argument to the analysis configuration as an interim measure for keeping the IDEs compatible with the version of the CLI on the master branch.

      Then proceed to update the Plugins/extensions to be able to be integrated with the new reports.
      I have tried running the VSCode extension with a version of the CLI that generates the PF4 reports and they don't open within the extension, which is to be expected really.

      Attachments

        Activity

          People

            josteele John Steele
            pcattana Philip Cattanach
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: