Quarkus (REST) behaves differently when having a parent POM

[timonzi]

Describe the bug

I have the problem described in #47471

Now I had the problem, that I wasn't able to reproduce the problem outside of our library projects - so in completely new projects. After some hours I figured out, that the problem (#47471) is only reproducible when I don't have a parent POM.

With the parent POM, the problem is not reproducible. When I delete the parent POM, the tests fail. So depending on the project structure, the behavior is different. This is pretty critical in my opinion.

Expected behavior

The behavior should always be the same. Regardless of the project structure.

When I create a library, I will write tests in this library. And these tests should work in the same way as when I put the tests in another project. Otherwise, I cannot guarantee the functionality without creating additional test projects (with other parent POM) and put the tests in there.

Actual behavior

The behavior differs depending on the project structure.

• With parent POM: The tests fail because of the HTTP 404
• Without parent POM: The tests are running fine

So it assume, that Quarkus scans the file system (depending on the projects structure) and behaves then differently if some information can be found there. But I don't know.

How to Reproduce?

Reproducer: https://github.com/timonzi/path-and-query-param/tree/with-parent-pom

1. Build the projects via the parent / top level POM (mvn clean install) => All tests are working
2. Delete the top level POM or comment out the modules
3. Build project path-and-query-param-usage (mvn clean install) => The tests will fail

See also the README.md

Output of uname -a or ver

Linux nb-timonz 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Output of java -version

OpenJDK 64-Bit Server VM Temurin-21.0.5+11 (build 21.0.5+11-LTS, mixed mode, sharing)

Quarkus version or git rev

3.20.0

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.6

Additional information

No response

[quarkus-bot]

/cc @FroMage (rest)

[gsmet]

Thanks for the reproducer. While extremely weird, there was indeed a bug that AFAICS is fixed in main.

And I think the fix is probably: #47746 .

[timonzi]

Thank you for the information!
But does this MR "only" fix the actual linked problem (#47471) or does it also change the behavior regarding the project structure?
Because this is not the first time that the behavior is different depending on whether the code is outside of my module structure or not - and those problems had nothing to do with Quarkus REST iirc. I don't remember which functionalities caused problems here, as they happened several years ago. But it can happen that we have to search for a long time until we find such an error.