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

Add noverify flag to the JVM for the dev mode #378

Merged
merged 1 commit into from
Jan 8, 2019

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Dec 21, 2018

This flag disables bytecode verification and therefore reduces the
startup time

Fixes: #340

@stuartwdouglas
Copy link
Member

I have been hesitant to add this because we are doing bytecode generation, so if we have a bug in our code if this flag is present it will manifest in a JVM crash.

As this only applies to dev mode I think this is ok, but we should have an option to re-enable this.

@geoand
Copy link
Contributor Author

geoand commented Dec 24, 2018

The fact that it only applies to dev mode is also why I think it's ok to add.

I would be glad to add a flag to disable this feature. What would you prefer it be called?

This flag disables bytecode verification and therefore reduces the
startup time.
Also introduce the preventnoverify maven option that prevents setting
the noverify JVM flag

Fixes: #340
@stuartwdouglas stuartwdouglas merged commit 6c07abd into quarkusio:master Jan 8, 2019
@stuartwdouglas stuartwdouglas added this to the 0.5.0 milestone Jan 8, 2019
@geoand geoand deleted the noverify branch January 8, 2019 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants