Property 'mainClass' not set in 'secondaryLauncher' block

[HGuillemet]

When defining a secondary launcher with Kotlin DSL:

jlink {
    secondaryLauncher {
        name = "my-additional-app"
        mainClass.set("org.example.MyAdditionalApp")
        args = listOf("--user", "emma")
    }
}

Gradle complains with:

Property 'mainClass' not set in 'secondaryLauncher' block

Is there something I'm doing wrong ?

BTW, the example in the documention for Kotlin DSL reads:

        mainClass = "org.example.MyAdditionalApp"

which also triggers an error:

Type mismatch: inferred type is String but Property<String!>! was expected

[airsquared]

Same issue with Groovy DSL.

Caused by: org.gradle.api.GradleException: Property 'mainClass' not set in 'secondaryLauncher' block
	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:67)
	at org.beryx.jlink.data.SecondaryLauncherData$_check_closure1.doCall(SecondaryLauncherData.groovy:39)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at org.beryx.jlink.data.SecondaryLauncherData.check(SecondaryLauncherData.groovy:38)
	at org.beryx.jlink.data.JlinkPluginExtension.secondaryLauncher(JlinkPluginExtension.groovy:182)
	at org.beryx.jlink.data.JlinkPluginExtension_Decorated.secondaryLauncher(Unknown Source)

jlink {
    ...
    launcher {
        noConsole = true
    }
    secondaryLauncher {
        name = 'blobsaver-console'
        mainClass = mainClassName
        noConsole = false
    }
}

[airsquared]

Managed to get past this by also specifying moduleName but then I run into adoptium/adoptium-support#769.

[airsquared]

Fixed in v3.0.0.