-
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
Tests fail after quarkus:dev run #7581
Comments
@gastaldi do you mind looking at it. |
I can reproduce this and does look like a blocker to me IMO. |
/cc @dmlloyd |
@aloubyansky this looks similar to the error we had in Gradle, no? |
@stuartwdouglas assigning it to you, as I got zero cycles today :( |
This is due to the classpath caching. Both |
Ah, of course, it's because now the whole app model is persisted instead of the deployment only part. The file name |
I wouldn't classify this as a blocker for the CR though. |
So we could either find a way to unify the work or segregate the cache for the two use cases (or three if we consider packaging as one). |
Actually, changing the file name by appending the launch mode to it would be a one line fix. Let me see if I can do that now. |
@aloubyansky hero! Fix merged. |
When running mvn package (no clean) after quarkus:dev, 1. tests fail 2. with a weird inlined exception in the console.
If
./mvnw clean package
is run, then no failure occurs.The text was updated successfully, but these errors were encountered: