|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +//docs/release_notes-7.1.0/master.adoc |
| 4 | + |
| 5 | + |
| 6 | +:_newdoc-version: 2.18.2 |
| 7 | +:_template-generated: 2024-07-01 |
| 8 | + |
| 9 | +:_mod-docs-content-type: REFERENCE |
| 10 | + |
| 11 | +[id="new-features-7-1-0_{context}"] |
| 12 | += New features |
| 13 | + |
| 14 | +This section provides the new features and improvements of the {ProductFullName} 7.1.0. |
| 15 | + |
| 16 | +.Support for analyzing applications managed with Gradle has been added to {ProductShortName} |
| 17 | + |
| 18 | +In earlier releases of {ProductFullName}, you could use {ProductShortName} to analyze Java applications managed only with Maven. With this update, {ProductShortName} can also extract dependencies from Gradle projects. As a result, you can now analyze applications that use Gradle instead of Maven. |
| 19 | + |
| 20 | +:FeatureName: Support for analyzing applications managed with Gradle |
| 21 | + |
| 22 | +include::developer-preview-feature.adoc[] |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +.Support for analyzing .NET applications has been added to {ProductShortName} |
| 27 | + |
| 28 | +In {ProductFullName} 7.1.0, you can use MTA to analyze Windows-only .NET framework applications to aid migration from version 4.5 or later to multi-platform .NET 8.0 running on OpenShift Container Platform. This feature is only available in the command-line interface (CLI). |
| 29 | + |
| 30 | +:FeatureName: Support for analyzing .NET applications |
| 31 | + |
| 32 | +include::developer-preview-feature.adoc[] |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +.Support for languages other than Java |
| 37 | + |
| 38 | +In {ProductFullName} 7.1.0, you can use {ProductShortName} to analyze .NET applications written in languages other than Java. To run analysis on .NET applications written in languages other than Java, add a custom rule set and do not specify a target language. |
| 39 | + |
| 40 | +:FeatureName: Support for languages other than Java |
| 41 | + |
| 42 | +include::developer-preview-feature.adoc[] |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +.Assessment and review statuses are now displayed in the {ProductShortName} UI |
| 47 | + |
| 48 | +In earlier releases of {ProductFullName}, the status of the assessment and the review was only displayed for applications. With this update, the status of the archetype assessment and review processes is displayed in the {ProductShortName} user interface (UI): |
| 49 | + |
| 50 | +* The assessment statuses are the following: |
| 51 | +** Completed: All required assessments completed. |
| 52 | +** InProgress: The assessment process is in progress. |
| 53 | +** NotStarted: The assessment process has not been started. |
| 54 | +* The review statuses are the following: |
| 55 | +** Completed: A review exists. |
| 56 | +** NotStarted: The review process has not been started. |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | +.New Insights feature has been added |
| 61 | + |
| 62 | +Tagging rules that earlier generated tags and showed the presence of technology also generate Insights now and show the location of code. While Insights do not impact the migration, they contain useful information about the technologies used in the application and their usage in the code. Insights do not have an effort and category assigned but might have a message and tag. You can view Insights in the Static report under the Insights tab. |
| 63 | + |
| 64 | +:FeatureName: Insights |
| 65 | + |
| 66 | +include::technology-preview.adoc[] |
| 67 | + |
| 68 | + |
| 69 | + |
| 70 | +.New {ProductShortName} CLI options are available to select language providers when analyzing multi-language applications |
| 71 | + |
| 72 | +In earlier releases of {ProductFullName}, you could not select specific language providers to run separately for the analysis of a multi-language application. With this update, you can use the new `--provider` {ProductShortName} command-line interface (CLI) option to explicitly set which language provider to run. |
| 73 | + |
| 74 | +The following CLI options are also available with this update: |
| 75 | + |
| 76 | +* `--list-providers` to list language providers supported for the analysis. |
| 77 | +* `--override-provider-settings` to override an existing supported language provider or to run your own unsupported provider. |
| 78 | + |
| 79 | +NOTE: You can now also configure supported language provider options in a provider’s configuration file. |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +.A new Task Manager page is now available in the {ProductShortName} UI |
| 84 | + |
| 85 | +In earlier releases of {ProductFullName}, tasks that were being performed and the queue of pending tasks were not displayed in the {ProductShortName} user interface (UI). With this update, a new Task Manager page is available to view the following information about the tasks that are queued: |
| 86 | + |
| 87 | +* *ID*: The ID of the task. |
| 88 | +* *Application*: The application name associated with the task. |
| 89 | +* *Status*: The status of the task, for example, *Scheduled*, *Pending*, *In progress*, *Succeeded*, or *Failed*. |
| 90 | +* *Kind*: The type of the task, for example, *analyzer* or *discovery*. |
| 91 | +* *Priority*: Priority of the task. The value is from zero to any positive integer. The higher the value in this column, the higher the priority of the task. |
| 92 | +* *Preemption*: It allows the scheduler to cancel a running task and free the resources for higher priority tasks. The values are *true* or *false*. |
| 93 | +* *Created By*: The name of the user who created the task. |
| 94 | + |
| 95 | + |
| 96 | + |
| 97 | +.Multiple applications can now be selected to filter the applications list in Application Inventory |
| 98 | + |
| 99 | +In earlier releases of {ProductFullName}, you could select only one application to filter the results on the Application Inventory page. With this update, you can select multiple applications as a single filter to display the list of applications corresponding to this filter. |
| 100 | + |
| 101 | + |
| 102 | + |
| 103 | +.Support for providing a single report when analyzing multiple applications on the CLI |
| 104 | + |
| 105 | +{mta-cli} was designed to analyze a single application and produce a report about that application. With this update, you can use the `--bulk` option of the `analyze` command to analyze multiple applications, one `analyze` command per application, but with a common output file for all of the reports. As described in the {UserCLIBookName}, this results in {mta-cli} generating a single analysis report for all the applications, instead of generating a separate report for each application. |
| 106 | + |
| 107 | +:FeatureName: Support for providing a single report when analyzing multiple applications on the CLI |
| 108 | + |
| 109 | +include::developer-preview-feature.adoc[] |
| 110 | + |
| 111 | + |
| 112 | +.New detailed reports generated during application analysis |
| 113 | + |
| 114 | +A new feature has been introduced that provides a more detailed analysis of your application. Two additional log reports, `issues.yaml` and `deps.yaml`, are now available for viewing and downloading. These reports contain details about unmatched rules. |
| 115 | + |
| 116 | +To enable the system to generate these reports, select the *Enable enhanced analysis details* checkbox in the *Advanced options* window during application analysis. |
0 commit comments