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

fix user guide describing wrong default behavior of @AnalyzeClasses #1406

Merged
merged 1 commit into from
Jan 18, 2025
Merged

fix user guide describing wrong default behavior of @AnalyzeClasses #1406

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
9 changes: 8 additions & 1 deletion docs/userguide/009_JUnit_Support.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ For further information see <<Controlling the Cache>>.
==== Controlling the Import

Which classes will be imported can be controlled in a declarative way through `@AnalyzeClasses`.
If no packages or locations are provided, the whole classpath will be imported.
If no packages or locations are provided, the package of the annotated test class will be imported.
You can specify packages to import as strings:

[source,java,options="nowrap"]
Expand Down Expand Up @@ -116,6 +116,13 @@ production code, and only consider code that is directly supplied and does not c
As explained in <<The Core API>>, you can write your own custom implementation of `ImportOption`
and then supply the type to `@AnalyzeClasses`.

To import the whole classpath, instead of just the package of the test class, use the option

[source,java,options="nowrap"]
----
@AnalyzeClasses(wholeClasspath = true)
----

==== Controlling the Cache

By default, all classes will be cached by location. This means that between different
Expand Down
Loading