-
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
Hibernate Validator warnings are displayed when optional ResourceBundles are missing #21694
Comments
This comment has been minimized.
This comment has been minimized.
Fixes quarkusio#21694 (cherry picked from commit 0a1eda3)
Hi, I still see complain about "message" bundle not found in
// I'm on gradle 7.1, kotlin 1.6.10, java 11, container build in windows |
Your problem is due to the fact that there is a
and when we are testing if a @aloubyansky @stuartwdouglas while not critical, this is yet another occurrence of the CL used to test if classes/resources are available at build time being polluted with the build artifacts. What we usually want to do is to test if the thing will be available at runtime (I remember I posted something somewhere about the Infinispan test server polluting the classpath big time). |
With #22673 merged, the following will fix it
|
@aloubyansky oh, that's very cool! I'll have a look at this once #22673 is in then. And I wonder if we should have a look at other occurrences, typically when we test if a class is present in the processors (we do that in several places). |
Yes, and I guess we could have a more convenient API for these kind of classpath resource look-ups. |
That was my next question :). |
@gsmet are you taking care of the issue or want me to do anything about it? |
I will implement what you described above but I will let you come up with the nicer API given I have very little knowledge of this area :). Once we have the API, I think I'll go through the processors to try to fix the issues we have with class detection. |
Instead of checking the CL, we check only the runtime elements so we are sure the elements will be available at runtime. Related to quarkusio#21694
#22938 will fix it once and for all. |
Describe the bug
When an app depending on the Hibernate Validator extension is package using the native build, the following messages are printed to the output:
Although that does no harm to the build, it may lead to confusion giving that those bundles are optional.
Expected behavior
Do not print any message if the bundle does not exist in the user's application
Actual behavior
The message is printed.
How to Reproduce?
mvn clean package -Dnative -DskipTests
Output of
uname -a
orver
Fedora 35
Output of
java -version
11
GraalVM version (if different from Java)
21
Quarkus version or git rev
2.5.0.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.8.4
Additional information
This issue was originated from a chat in Zulip.
Also it seems that this snippet may need to be enhanced to check if the bundle really exists
The text was updated successfully, but these errors were encountered: