While reviewing a failure in our rhbq-3.15-acceptance/job/rhbq-3.15-rhel8-jdk17-extensions-combinations-ts/ :

java.lang.RuntimeException: mvn failed (executed [mvn, -Dmaven.repo.local=/home/hudson/hudson_workspace/workspace/rhbq-3.15-rhel8-jdk17-extensions-combinations-ts/test-suite/rh-quarkus-platform-3.15.3.GA-maven-repository/maven-repository/, -Dquarkus-plugin.version=3.15.3.redhat-00001, -Dquarkus.platform.group-id=com.redhat.quarkus.platform, -Dquarkus.platform.artifact-id=quarkus-bom, -DquarkusRegistryClient=false, package, -DskipTests, -DskipITs], return code 1) 

I discovered some files missing (pom.xml) from maven repository in kotlin-maven-plugin

maven-repo-zips/rh-quarkus-platform-3.15.3.CR1-maven-repository/rh-quarkus-platform-3.15.3.GA-maven-repository/maven-repository/org/jetbrains/kotlin/kotlin-maven-plugin

the generated project specifies the following Kotlin version: 

<kotlin.version>2.0.10.redhat-00001</kotlin.version> 

Having a productized version of the kotlin-maven-plugin defined in the application is causing build failures due to the missing pom.xml file in the Maven repository.

In previous versions, such as 3.15.2, generating a Kotlin application used: 

kotlin.version>2.0.10</kotlin.version> 

This discrepancy is cauising build failure using Kotlin, similar to the issue described here: https://issues.redhat.com/browse/QUARKUS-4892

Although we do not officially support Kotlin, we allow customers to use it as we aim to ensure the same user experience between upstream and downstream.

Thank you