-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
False
-
False
-
+
-
This is the default Maven configuration for a Quarkus application:
<properties>
<quarkus-plugin.version>2.2.3.Final</quarkus-plugin.version>
<quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id>
<quarkus.platform.group-id>io.quarkus</quarkus.platform.group-id>
<quarkus.platform.version>2.2.3.Final</quarkus.platform.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
<version>${quarkus.platform.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- .... -->
</dependencies>
<build>
<plugins>
<plugin>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>quarkus-maven-plugin</artifactId>
<version>${quarkus.platform.version}</version>
<!-- .... -->
We added the "com.redhat.quarkus:quarkus-universe-bom" for backward compatilibity, the problem is that "quarkus-maven-plugin also changed from "com.redhat.quarkus" to "com.redhat.quarkus.platform", so doing "-Dquarkus.platform.group-id=com.redhat.quarkus -Dquarkus.platform.artifact-id=quarkus-universe-bom" won't still be not compatible for users coming from RHBQ 1.11.