Concatenate io.netty.versions.properties instead of ignoring them

[gsmet]

Fixes #16662

[quarkus-bot]

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building a690a9b

Status	Name	Step	Test failures	Logs	Raw logs
✖	Native Tests - Windows - hibernate-validator	Build	⚠️ Check →	Logs	Raw logs

[geoand]

Could we introduce an enhancement in the Maven uberjar test, that ensures that calls the Netty class mentioned in the issue?

[quarkus-bot]

Failing Jobs - Building 524a9fd

Status	Name	Step	Test failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs
✖	JVM Tests - JDK 15	Build	Test failures	Logs	Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 15 #

📦 extensions/vertx-http/deployment

✖ io.quarkus.vertx.http.testrunner.includes.ExcludePatternTestCase.checkTestsAreRun line 58 - More details - Source on GitHub

[gsmet]

@stuartwdouglas the build failure above looks suspicious.

[stuartwdouglas]

I am looking into it. It looks like somehow an additional test run is triggered after a single change.

[stuartwdouglas]

It's because of this:

quarkus/test-framework/junit5-internal/src/main/java/io/quarkus/test/QuarkusDevModeTest.java

Line 603 in 7ca3307

Files.setLastModifiedTime(path, FileTime.fromMillis(System.currentTimeMillis()));

Updating the file timestamp can result in a race where the test polling timer sees two changes, and runs the tests a second time.