You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some time I was observing the following message while building Quarkus application.
[INFO] --- quarkus-maven-plugin:2.10.1.Final:build (default) @ application ---
[WARNING] [io.quarkus.arc.processor.BeanArchives] Failed to index String: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD@3ee86eb7
[INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in 12810ms
Today I've found what is causing this issue. I had the following code in one of my Qute templates.
kucharzyk
changed the title
Qute - Failed to index String: Class does not exist in ClassLoader QuarkusClassLoade
Qute - Failed to index String: Class does not exist in ClassLoader
Jul 3, 2022
fixes: quarkusio#26524
When `TypeInfos.create` is looking for a parameter declaration type, it checks couple of options and fallback to prefix `java.lang`. The Qute reference guide contains an example of parameter declaration using only `{@string foo}` without `java.lang`, thus when user follows the example, he should not be warned.
Describe the bug
For some time I was observing the following message while building Quarkus application.
Today I've found what is causing this issue. I had the following code in one of my Qute templates.
I was getting this annoying waring in logs because of this code.
After changing template code issue has been resolved.
This warning message is missleading and it should be fixed. At least we need to add real problem couse to log message.
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: