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

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

Merged

Conversation

codecholeric
Copy link
Collaborator

The user guide claims that without specifying anything @AnalyzeClasses will import the whole classpath.
This is not true anymore since release 1.0, because we changed the default behavior to import the package of the annotated test class.
The user guide now reflects this correctly and also mentions the option wholeClasspath to restore the old behavior.

Resolves: #1401

The user guide claims that without specifying anything `@AnalyzeClasses` will import the whole classpath.
This is not true anymore since release 1.0, because we changed the default behavior to import the package of the annotated test class.
The user guide now reflects this correctly and also mentions the option `wholeClasspath` to restore the old behavior.

Signed-off-by: Peter Gafert <peter.gafert@archunit.org>
@codecholeric codecholeric merged commit 477144a into main Jan 18, 2025
21 checks passed
@codecholeric codecholeric deleted the fix-userguide-describing-wrong-analyzeclasses-behavior branch January 18, 2025 23:55
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.

Behavior of @AnalyzeClasses different than documentation
1 participant