Closed Karm closed 9 months ago
Fixed with maven update for newer quarkus.
@Karm where is the fix?
I needed these:
commit 304fd64a03d4c64920ef3729de745b3304cfd194
Author: Severin Gehwolf <sgehwolf@redhat.com>
Date: Wed Sep 6 19:35:56 2023 +0200
Fix final name
diff --git a/apps/quarkus-json/pom.xml b/apps/quarkus-json/pom.xml
index 57254d0..cfb1aa3 100644
--- a/apps/quarkus-json/pom.xml
+++ b/apps/quarkus-json/pom.xml
@@ -15,7 +15,7 @@
<properties>
<quarkus.version>${global.quarkus.version}</quarkus.version>
- <final.name>${final.name}</final.name>
+ <final.name>quarkus-json-test</final.name>
</properties>
<dependencyManagement>
and
commit 52608c50db7ae8b43e77da331e0f37249fe7a47c (HEAD -> master)
Author: Severin Gehwolf <sgehwolf@redhat.com>
Date: Wed Sep 6 19:46:58 2023 +0200
Fix vertex-web (now reactive-routes)
diff --git a/apps/quarkus-vertx/pom.xml b/apps/quarkus-vertx/pom.xml
index 4bbe1d3..7d47c9b 100644
--- a/apps/quarkus-vertx/pom.xml
+++ b/apps/quarkus-vertx/pom.xml
@@ -48,7 +48,7 @@
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
- <artifactId>quarkus-vertx-web</artifactId>
+ <artifactId>quarkus-reactive-routes</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
@jerboaa The thing is that:
@Karm Responses in-line below.
new Quarkus requires Maven 3.8.8, so Mandrel Integration Test suite too, that is what I meant by fixed. Maven update in test infra.
Not sure why a maven upgrade would fix this. It seems more likely that a not-clean ~/.m2
fixes it.
${final.name} is because of places like https://github.com/Karm/mandrel-integration-tests/blob/master/testsuite/src/it/java/org/graalvm/tests/integration/utils/BuildAndRunCmds.java#L97 I guess there could be some default though. If you execute it without anything, it's invalid circular reference.
OK. This sounds like we need something like default.final.name
in a profile which activates if default.final.name
is not provided and the tests in BuildAndRunCmds.java
updated accordingly. I don't see how quarkus-json
can build with only mvn clean package
otherwise.
quarkus-vertx-web
It's quarkus-reactive-routes
since 2.13.7.Final
?:
$ cat ~/.m2/repository/io/quarkus/quarkus-vertx-web/2.13.7.Final/quarkus-vertx-web-2.13.7.Final.pom
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<artifactId>quarkus-relocations-parent</artifactId>
<groupId>io.quarkus</groupId>
<version>2.13.7.Final</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>quarkus-vertx-web</artifactId>
<distributionManagement>
<relocation>
<artifactId>quarkus-reactive-routes</artifactId>
<message>The artifact ${project.artifactId} is now named quarkus-reactive-routes. Please update your dependency.</message>
</relocation>
</distributionManagement>
Not sure why a maven upgrade would fix this. It seems more likely that a not-clean ~/.m2 fixes it.
Updating from Maven 3.6.3 is needed for the latest Quarkus. The text of this issue is misleading. I jotted it down incompletely. Maven version has nothing to do with the final.name issue.
OK. This sounds like we need something like default.final.name in a profile which activates if default.final.name is not provided...
That would work :+1:
I don't see how quarkus-json can build with only mvn clean package otherwise.
It does not in the current form.
It's quarkus-reactive-routes since 2.13.7.Final?
Great, let's update it then :pray:
Sorry for the inconvenience. Apparently some housekeeping is in order.
PR is updated to allow for the final name customization. Please review! Thanks.