You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built in search on docs.junit.org isn't able to find exact text matches, or if it does the results are incomplete. This is mildly annoying because this information should be easily discoverable and lowers the trust in the built in search function.
The current workaround, to switch the view to "Single Page" and then using the built in browser search works well enough.
Activity
[-]Build in search can not find some strings[/-][+]Built in search can not find some strings[/+]Tanixq commentedon May 12, 2026
I investigated this issue and traced the behavior to the
@antora/lunr-extensionsearch implementation used by the JUnit documentation site.I opened an upstream merge request with a proposed fix here:
https://gitlab.com/antora/antora-lunr-extension/-/merge_requests/113
The change improves discoverability for dotted identifiers such as:
org.junit.jupiter.api.Assumptionsjunit.platform.stacktrace.pruning.enabledwhile preserving existing exact-match search behavior as much as possible.
marcphilipp commentedon Sep 18, 2026
@Tanixq Thanks! Did you see the comment on the PR to create an issue first?
Since Lunr.js seems abandoned, I opened a thread on Antora's Zulip asking for alternatives. https://pagefind.app/ looks promising and there's even an Antora extension for it but it's not a drop-in replacement.