-
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 template detection has changed on Windows for templates in project dependencies #42571
Comments
/cc @mkouba (qute) |
Yeah there's a good chance that it's related. |
Ah it's on Windows... very nice... |
@aloubyansky I think this is probably related to what you made me change in my patch to use the container path instead of the root path for In Either we go back to what I initially did or Note that I don't have Windows so I wasn't able to reproduce the issue but I'm pretty sure that's the issue here. |
@michalvavrik I created #42588 to get back to the initial behavior of my patch. Any chance you could check if it fixes the issue on Windows? |
Technically it's not a problem (it's just setting up CI or creating OpenStack or AWS instance), but I am fighting with time for next 5 days. Ideally, I can just confirm when it is merged (rerun CI). |
@michalvavrik sure, let's do that, I think it's very likely that it is the issue. |
Fix did the trick and Windows CI is fixed. Thank you. |
Awesome! Thanks for the detailed report and the confirmation! |
The container path is the path of the container (could be a directory or an archive and shouldn't be used for browsing. The root path is the path of the root. In the case of an archive, it's actually a ZipPath, which can be used to browse the archive. Fixes quarkusio#42571 (cherry picked from commit 6dd6150)
The container path is the path of the container (could be a directory or an archive and shouldn't be used for browsing. The root path is the path of the root. In the case of an archive, it's actually a ZipPath, which can be used to browse the archive. Fixes quarkusio#42571 (cherry picked from commit 6dd6150)
The container path is the path of the container (could be a directory or an archive and shouldn't be used for browsing. The root path is the path of the root. In the case of an archive, it's actually a ZipPath, which can be used to browse the archive. Fixes quarkusio#42571
Describe the bug
I have app that has Jakarta REST resources and Qute templates in separate Maven project and imports this project as dependency to Quarkus application. Now I can see that template is not detected anymore in 999-SNAPSOT. It seems like behavior has changed in last 24 hours. I have looked to merge commits and only thing that seems related by description is #42492 (cc @gsmet ) but I didn't try it. I checked
io.quarkus.qute.deployment.QuteProcessor#collectTemplates
though and it seems like that PR touched related code.Expected behavior
Behavior on Linux and Windows should be same or differences should be documented.
Actual behavior
Build fails and exception is raised:
How to Reproduce?
Steps to reproduce the behavior:
git clone git@github.com:quarkus-qe/quarkus-test-suite.git
cd quarkus-test-suite/qute/multimodule
mvn clean verify
Output of
uname -a
orver
Microsoft Windows Server 2022 10.0.20348
Output of
java -version
Temurin 17.0.12+7
Quarkus version or git rev
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
Additional information
You can see logs here: https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/10401726443/job/28805582860
And previous runs here: https://github.com/quarkus-qe/quarkus-test-suite/actions/workflows/daily.yaml
The text was updated successfully, but these errors were encountered: