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

Clarify how to use processExistingClasses in debugging.adoc #3130

Merged
merged 2 commits into from Aug 1, 2022
Merged

Clarify how to use processExistingClasses in debugging.adoc #3130

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e26005
Update debugging.adoc
kicmeri Jul 27, 2022
31e8db2
Clarify how to use processExistingClasses in debugging.adoc
kicmeri Jul 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/asciidoc/debugging.adoc
View file
Open in desktop
Expand Up @@ -433,7 +433,7 @@ ReactorDebugAgent.init();
====

TIP: Since the implementation will instrument your classes when they are loaded,
the best place to put it is before everything else in your main(String[]) methood:
the best place to put it is before everything else in your main(String[]) method:
====
[source,java]
----
Expand All @@ -444,7 +444,7 @@ public static void main(String[] args) {
----
====

You may also re-process existing classes if you cannot run the init eagerly (e.g. in the tests):
You may also re-process existing classes with `processExistingClasses()` if you cannot run the init eagerly. For example, in https://junit.org/junit5/docs/current/user-guide/#launcher-api-listeners-custom[JUnit5 tests from a `TestExecutionListener`] or even in the class `static` initializer block:
====
[source,java]
----
Expand Down