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.

Sign up for GitHub

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

Jump to bottom

Fixed typo in building-native-image-guide #2988

Merged
merged 1 commit into from
Jun 26, 2019
Merged

Fixed typo in building-native-image-guide #2988

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/src/main/asciidoc/building-native-image-guide.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ When running tests this way, the only things that actually run natively are you
you can only test via HTTP calls. Your test code does not actually run natively, so if you are testing code
that does not call your HTTP endpoints, it's probably not a good idea to run them as part of native tests.

If you share your test class between JVM and native execusions like we advise above, you can mark certain tests
If you share your test class between JVM and native executions like we advise above, you can mark certain tests
with the `@DisabledOnSubstrate` annotation in order to only run them on the JVM.

== Creating a container
Expand Down