'@JvmOverloads' annotation cannot be used on constructors of annotation classes since 1.4

Reports @JvmOverloads on constructors of annotation classes because it's meaningless.

There is no footprint of @JvmOverloads in the generated bytecode and Kotlin metadata, so @JvmOverloads doesn't affect the generated bytecode and the code behavior.

@JvmOverloads on constructors of annotation classes causes a compilation error since Kotlin 1.4.

Example:

annotation class A @JvmOverloads constructor(val x: Int = 1)

After the quick-fix is applied:

annotation class A constructor(val x: Int = 1)

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.

ProhibitJvmOverloadsOnConstructorsOfAnnotationClassesMigration

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 | Kotlin | Migration

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 ProhibitJvmOverloadsOnConstructorsOfAnnotationClassesMigration

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

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025