Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-3169

Analysis of Java applications fails when a POM file is not available

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Blocker Blocker
    • MTA 7.1.0
    • MTA 7.0.3
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Critical
    • ?
    • Yes

      Description of problem:

      Analysis of an application that doesn't have a POM file present on its root path will fail. This is a regression from MTA 6, which didn't require any dependency management files to be present for the analysis to run.

      This issue is especially relevant for the migration of legacy applications that might use Ant or Ivy. Even if the language server doesn't support them, which is the case, it should be possible to analyze those applications in source mode.

       Version-Release number of selected component (if applicable):

      MTA 7.0.3

       How reproducible:

      Always

       Steps to Reproduce:

      1. Analyze the application at https://github.com/WASdev/sample.DefaultApplication/tree/main/original

      Actual results:

      Analysis takes a long time and fails (see attached log)

      Expected results:

      Analysis succeeds.

      Additional info:

        1. 1719478434811(2).yaml
          10.06 MB
          Ramon Roman Nissen
        2. Screenshot from 2024-08-06 14-22-00.png
          171 kB
          Karishma Punwatkar
        3. Screenshot from 2024-08-07 11-19-23.png
          43 kB
          Karishma Punwatkar

              jortel Jeff Ortel
              rromanni@redhat.com Ramon Roman Nissen
              Karishma Punwatkar Karishma Punwatkar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: