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

Analysing multiple EAR files via Eclipse Plugin

XMLWordPrintable

    • Hide

      I selected 3 EAR files for analysis and when the analysis was complete all 3 applications appeared in the Issue Explorer window.

      In the /home/pcattana/workspace/.metadata/.plugins/org.jboss.tools.windup.model/reports/RHAMTAnythingtoEAP7/
      there is a sub-directory for each of the EAR files analysed.

      The Report output is definitely there for each EAR file.

      However in the console panel, Reports tab, I can't navigate to the to the index.html for a different application.

      Nor can does there appear to be a way of interacting with the Issue Explorer or Project Explorer panels to bring the other applications analysed into context on the Reports tab.

      Show
      I selected 3 EAR files for analysis and when the analysis was complete all 3 applications appeared in the Issue Explorer window. In the /home/pcattana/workspace/.metadata/.plugins/org.jboss.tools.windup.model/reports/RHAMTAnythingtoEAP7/ there is a sub-directory for each of the EAR files analysed. The Report output is definitely there for each EAR file. However in the console panel, Reports tab, I can't navigate to the to the index.html for a different application. Nor can does there appear to be a way of interacting with the Issue Explorer or Project Explorer panels to bring the other applications analysed into context on the Reports tab.
    • Sprint 42
    • None

      If multiple EAR files are imported and selected for analysis in a single run theere are 3 separate directories populated with Reports pertaining to each application (EAR file).
      However only one of them is accessible via the console tab within JBDS

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

                Created:
                Updated:
                Resolved: