-
Notifications
You must be signed in to change notification settings - Fork 325
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
Require separate advice class #2101
Require separate advice class #2101
Conversation
Avoids class loading issues when the advice refers to library classes. This allows to validate the advice class when the instrumentations get initialized as opposed to on indy bootstrap. That caches more errors and fails faster.
getClass().getName() + "$AdviceClass"
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, good idea to use AdviceClass
as a generic default to avoid having to properly find dozen of relevant class names.
|
What does this PR do?
Avoids class loading issues when the advice refers to library classes.
This allows to validate the advice class when the instrumentations get initialized
as opposed to on indy bootstrap.
That caches more errors and fails faster.
relates to #1337