-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
io.quarkus.qute.deployment.QuteProcessor#collectTemplates threw exception #25751
Comments
/cc @mkouba |
private void scan(Path root, Path directory, String basePath, BuildProducer<HotDeploymentWatchedFileBuildItem> watchedPaths,
BuildProducer<TemplatePathBuildItem> templatePaths,
BuildProducer<NativeImageResourceBuildItem> nativeImageResources,
QuteConfig config)
throws IOException {
try (Stream<Path> files = Files.list(directory)) {
Iterator<Path> iter = files.iterator();
while (iter.hasNext()) {
Path filePath = iter.next();
if (Files.isRegularFile(filePath)) {
LOGGER.debugf("Found template: %s", filePath);
String templatePath = root.relativize(filePath).toString(); // FAILS HERE
if (File.separatorChar != '/') {
templatePath = templatePath.replace(File.separatorChar, '/');
}
|
Is there any reason |
I have no idea. Did you try to use |
I tried and it doesn't work, so it's not that simple. From Maven it works and I get this:
From Eclipse I get this:
I really wonder why the |
Well, whatever, I found a fix, will send a PR soon. |
But damn, this is just a weird bug. |
Indeed 🤔 |
Describe the bug
Sometimes I'm getting this issue when launching tests in Eclipse IDE. I can't reproduce when running tests from Maven.
I'll attach a debugger to figure it out.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: