-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qute: ultimate fix for the problem with registering NativeImageResourceBuildItem correctly on Windows #40158
Conversation
- previously, we used incorrectly an OS-specific relative path
Looks like this needs to be backported too? |
Yes, if possible... |
Status for workflow
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can merge but I wouldn't qualify it as ultimate
as I think the issue with NativeImageResourceBuildItem
being brittle is not fixed :)
watchedPaths.produce(new HotDeploymentWatchedFileBuildItem(osAgnosticResourcePath, restartNeeded)); | ||
nativeImageResources.produce(new NativeImageResourceBuildItem(osSpecificResourcePath)); | ||
watchedPaths.produce(new HotDeploymentWatchedFileBuildItem(resourcePath, restartNeeded)); | ||
nativeImageResources.produce(new NativeImageResourceBuildItem(resourcePath)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's good enough, probably but we still have the issue that this is gonna be interpreted like a regexp, right? So .
will mean any char for instance?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but that's another issue that should be addressed in a separate pull request.
Yes, it's "ultimate" from Qute POV, not from the core POV ;-) |
@mkouba@ @gastaldi @gsmet : Unfortunately, I have some problems with these additions. I am running on Linux and have some Does #40067 resolve this already? Sadly, I don't really have time to contribute here for the next 2 months, sorry! |
In which mode does it happen? Dev/prod? We do have a test for the default value of CC @aloubyansky |
@mkouba : super interestingly, it does NOT occur in By the way: the
But I have also tried to set basePath to "/foo", "templates/foo", "/templates/foo", but all of them produce a |
@mzellho Do you run the tests from the command line or IDE?
|
@mkouba: Well, in reality my template / static method is not called Both, I had it failing on our Build Server when running a |
Sure ;-)
Ok, your build server is also Linux? Does it fail if you run the tests locally with |
Yes, both are on Linux and it also fails locally with a |
Uf, I wasn't able to reproduce the problem locally with the qute-quickstart which also contains What version of Quarkus do you use? |
|
So, reproduced, but I don't think it would affect too many people, and likely it also doesn't need to be fixed urgently. The scenario is that there is a I will also share the reproducer in a bit / after lunch. |
Pls create a new issue and attach the reproducer there. Thanks a lot! |
alright, thank you --> #40366 |
This pull request should contain the ultimate fix for the problem with registering
NativeImageResourceBuildItem
correctly on Windows.It also fixes #40055.
There's a zulip topic about the contract of
NativeImageResourceBuildItem
: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/NativeImageResourceBuildItem.20-.20format.20of.20resource.20params.3F. However, this problem will be probably addressed in a separate PR.We've also added the
quarkus-qute-integration-test
module into the native Windows CI category. Hopefully, this will improve our ability to detect this kind of problems.