Inspectopedia 2025.2 Help

Unnecessary fully qualified name

Reports fully qualified class names that can be shortened.

The quick-fix shortens fully qualified names and adds import statements if necessary.

Example:

class ListWrapper { java.util.List<Integer> l; }

After the quick-fix is applied:

import java.util.List; class ListWrapper { List<Integer> l; }

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

UnnecessaryFullyQualifiedName
Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Java | Code style issues

Configure the inspection:

Use the Ignore in Java 9 module statements option to ignore fully qualified names inside the Java 9 provides and uses module statements.

In Settings | Editor | Code Style | Java | Imports, use the following options to configure the inspection:

  • Use the Insert imports for inner classes option if references to inner classes should be qualified with the outer class.

  • Use the Use fully qualified class names in JavaDoc option to allow fully qualified names in Javadocs.

Inspection options

Here you can find the description of settings available for the Unnecessary fully qualified name inspection, and the reference of their default values.

Ignore in Java 9 module statements

Default value:

Selected

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection UnnecessaryFullyQualifiedName

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Inspection Details

By default bundled with:

IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025