Native image - Correct Windows paths in resources

[melloware]

Fix #31307: Correct Windows paths in native image

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not contain an issue number (use Fix #1234 in the description instead)

This message is automatically generated by a bot.

[maxandersen]

this probably fixes it but why is the resource using non portable paths to begin with? should be platform neutral before it gets here.

[zakkak]

I agree, this doesn't seem right. We should tackle this earlier. At this point the path has already been written by Quarkus to a txt file and parsed in the wrong format.

[melloware]

You guys are the experts 😄

[gsmet]

@zakkak will you have a look at this issue?

[zakkak]

Sure, but the sooner I will probably be able to have a look at it will be late next week.

In the meantime, #31185 is now merged, @melloware could you please confirm the issue is still present in Quarkus main?

[melloware]

I am running on 2.16.3 not on SNAPSHOT so I have not confirmed it in main yet. Will try to get to it.

[melloware]

Agreed! But it's outside my depth of knowledge of why it's wrong when it gets here.

[Karm]

@zakkak I will drive this issue to a conclusion in #31307
I have Docker Desktop and Podman for Windows up and some slashes hunt exps https://github.com/quarkusio/quarkus/pull/25867/files

[melloware]

@Karm would you like me to close this PR?

[Karm]

This is not the root cause for Quarkus Native Primefaces Windows problems. Let me close the PR now.
We carry on in #31307

• Podman for Windows based run needs Q patches (I have it locally, PR pending)
• Docker Desktop based run goes all the way up to starting the test container
• pending PR to Prime faces integration tests to make it happen (custom Dockerfile installs fontconfig, uses quarkus-container-image-docker flow)

Both Podman and Docker though get stuck on a locked logfile target/quarkus.log. So that's what I am looking into now.
I think if we explicitly open just for reading the Windows lock might let us.

[melloware]

Great work. I think there will also be a bunch of open Native Windows tickets you can close here too once done as I found about 3-4 issues that I am pretty sure are already fixed.