-
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
Runtime initialization of some imageio related classes #12912
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be done in core as these classes are in the JDK and it's not a RESTEasy specific thing.
@gsmet OK, I placed them there because I saw resteasy triggering the instantiation of the classes but you are probably right. Should I create a new ImageIOProcessor in core or should I use an existing processor? Thanks. |
I would create a new one. There's a good chance we will need more logic there :). |
Thanks! |
AWT support in native-image is currently being worked on, so this should be removed in the future. Related quarkusio/quarkus#12912
AWT support in native-image is currently being worked on, so this should be removed in the future. Related quarkusio/quarkus#12912
AWT support in native-image is currently being worked on, so this should be removed in the future. Related quarkusio/quarkus#12912
@gsmet FYI this will probably not be needed once GraalVM CE 21.0 is out |
Closes: #12535