Skip to content
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

Cache signatures so that multiple runs of the mojo can reuse loaded signatures #165

Merged
merged 1 commit into from Jun 11, 2021

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Jun 9, 2021

Loading JDK signatures can take more than half a second, so when the build contains lots of modules, it can save a lot of time

…ignatures

Loading JDK signatures can take more than half a second, so when the build contains lots of modules, it can save a lot of time
@gnodet
Copy link
Contributor Author

gnodet commented Jun 9, 2021

This is interesting mainly in the context of mvnd where the mojo class loaders are reused. In a traditional maven build, the class loaders are deleted after each mojo run, so there would be no benefit.
@hboutemy @olamy

@olamy olamy merged commit f8df3fe into mojohaus:master Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants