Procedure

1. From the Oracle JDK download page, download the JDK tar.gz file suitable for your system.

   Note

   You need to accept the Oracle license agreement to proceed.

   Alternatively, you can download JDK by using the command-line interface:

   $ wget https://download.oracle.com/java/11/latest/<jdk-file>

2. Extract the tar.gz file:

   $ tar -xzf <jdk-file>

3. Optional: To make JDK available system-wide, move the extracted folder to the /opt directory:

   $ sudo mv <jdk-extracted-folder> /opt/<jdk-file>

4. Set up the JAVA_HOME environment variable and add the JDK bin directory to the PATH variable:

   1. Open the .bashrc file:

      $ nano ~/.bashrc

   2. Add the following lines to the file:

      export JAVA_HOME=/opt/<jdk-file>
      export PATH=$PATH:$JAVA_HOME/bin

   3. Save the file and close it.

   4. To apply the new changes, reload the file:

      $ source ~/.bashrc

Procedure

1. From the Eclipse download page, download the required Eclipse IDE tar.gz file, for example, Eclipse IDE for Java Developers.

2. Extract the tar.gz file:

   $ tar -xzf <file_name>.tar.gz

3. Optional: To make Eclipse available system-wide, move the extracted folder to the /opt directory:

   $ sudo mv eclipse /opt/eclipse

4. Optional: To make Eclipse launch from the command line, create a symbolic link to the executable:

   $ sudo ln -s /opt/eclipse/eclipse /usr/bin/eclipse

5. Optional: To launch Eclipse from you application menu, create a desktop entry:

   1. Create a new eclipse.desktop file:

      sudo nano /usr/share/applications/eclipse.desktop

   2. Add the following content to the eclipse.desktop file:

      [Desktop Entry]
      Name=Eclipse IDE 2024-03
      Type=Application
      Exec=/opt/eclipse/eclipse
      Terminal=false
      Icon=/opt/eclipse/icon.xpm
      Comment=Intergrated DEvelopment Environment
      NoDisplay=false
      Categories=Development;IDE;
      Name[en]=Eclipse IDE 2024-03

Procedure

1. Launch Eclipse.
2. From the menu bar, select Help Install New Software.
3. Add the JBoss Tools update website by specifying the https://download.jboss.org/jbosstools/photon/development/updates/ location.

Procedure

1. Launch Eclipse.
2. From the menu bar, select Help → Install New Software.
3. Next to the Work with field, click Add.
4. In the Name field, enter MTA.
5. In the Location field, enter https://marketplace.eclipse.org/content/migration-toolkit-applications-mta and click OK.

6. Select the Java version to use.

   • If using Java 11, in the JRE list, select JavaSE 11.
   • If using Java 17, leave the JRE selection unchanged.

7. Select all the JBoss Tools - MTA check boxes and click Next.
8. Review the installation details and click Next.
9. Accept the terms of the license agreement and click Finish.
10. Restart Eclipse.

Procedure

1. Click Window → Perspective → Open Perspective → Other.

2. Select MTA and click OK.

   The following components are displayed:

   • Issue Explorer displays the migration issues identified by the MTA plugin.

   • MTA Server is a separate process that analyzes projects, flags migration issues, and generates reports.

     You can start, stop, and view the status of the MTA server in the Issue Explorer.

   • Issue Details displays detailed information about a selected issue, including the hint, severity, and any additional resources.

   • MTA Report is an HTML report generated by the MTA plugin. From the report landing page you can navigate to detailed reports, such as Application Details, Issues, and Dependencies.

     Note

     The report is not generated by default. You must select the Generate Report option in the run configuration.

Procedure

1. In the Issue Explorer, click the MTA icon ( ) to create a run configuration.

2. On the Input tab, complete the following fields:

   1. Select a migration path.
   2. Beside the Projects field, click Add and select one or more projects.

   3. Beside the Packages field, click Add and select one or more the packages.

      Note

      Specifying the packages for analysis reduces the run time. If you do not select any packages, all packages in the project are scanned.

3. On the Options tab, you can select Generate Report to generate an HTML report. The report is displayed in the Report tab and saved as a file.

   Other options are displayed. See About MTA command-line arguments in the CLI Guide for details.

4. On the Rules tab, you can select custom rulesets that you have imported or created for the MTA plugin.
5. Click Run to start the analysis.

Procedure

1. In the MTA perspective, click the Run button ( ) and select a run configuration.

   The MTA plugin analyzes your projects. The Issue Explorer displays migration issues that are detected with the ruleset.

2. When you have finished analyzing your projects, stop the MTA server in the Issue Explorer to conserve memory.

Procedure

1. Click Window → Show View → Issue Explorer.

2. Optional: Filter the issues by clicking the Options menu , selecting Group By and an option.

   

3. Right-click and select Issue Details to view information about the issue, including its severity and how to address it.

   The following icons indicate the severity and state of an issue:

   Table 3.1. Issue icons

   Icon	Description
   	The issue must be fixed for a successful migration.
   	The issue is optional to fix for migration.
   	The issue might need to be addressed during migration.
   	The issue was resolved.
   	The issue is stale. The code marked as an issue was modified since the last time that MTA identified it as an issue.
   	A quick fix is available for this issue, which is mandatory to fix for a successful migration.
   	A quick fix is available for this issue, which is optional to fix for migration.
   	A quick fix is available for this issue, which may potentially be an issue during migration.

4. Double-click an issue to open the associated line of code in an editor.

Procedure

1. Click the Rulesets tab.
2. Expand System to view system rulesets or Custom to view custom rulesets.
3. Expand a ruleset.
4. Double-click a rule to open it in a viewer.
5. Click the Source tab to view the XML source of the rule.

Procedure

1. Click the Rulesets tab.
2. Click the Create Ruleset icon ( ).
3. Select a project and a directory for the ruleset.

4. Enter the file name.

   Note

   The file must have the extension .windup.xml.

5. Enter a ruleset ID, for example, my-ruleset-id.
6. Optional: Select Generate quickstart template to add basic rule templates to the file.
7. Click Finish.
8. The ruleset file opens in an editor and you can add and edit rules in the file.
9. Click the Source tab to edit the XML source of the ruleset file.

Procedure

1. Click the Rulesets tab.
2. Click the Import Ruleset icon ( ).

3. Browse to and select the XML rule file to import.

   The custom ruleset is displayed when you expand Custom on the Rulesets tab.

Procedure

1. Click the Rulesets tab.
2. Click the Arrow icon ( ) and select Submit Ruleset.

3. Complete the following fields:

   • Summary: Describe the purpose of the rule. This becomes the title of the submission.
   • Code Sample: Enter an example of the source code that the rule should run against.
   • Description: Enter a brief description of the rule.
4. Click Choose Files and select the ruleset file.
5. Click Submit.