-
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
VertxCoreProcessor and HibernateValidatorProcessor bytecode transformers are safe to be cached #40197
Conversation
This comment has been minimized.
This comment has been minimized.
The failed test has been unstable for a long time apparently :( |
Should probably be rebased on top of #40203 |
It passed all tests but I'm pushing a new version now which uses the Builder to create the same build-items, so making it better maintainable and to avoid conflicts with #40203 |
c9d9ca6
to
fdf0a03
Compare
This comment has been minimized.
This comment has been minimized.
fdf0a03
to
c43ea49
Compare
This comment has been minimized.
This comment has been minimized.
c43ea49
to
58f06f7
Compare
This comment has been minimized.
This comment has been minimized.
…ers are safe to be cached
58f06f7
to
ccd92be
Compare
Status for workflow
|
@mkouba as the topic is fresh in your mind, could I ask you for a review? |
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.
👍 seems safe to cache both transformations.
This is a small improvement affecting memory consumption during live-reload.