-
Notifications
You must be signed in to change notification settings - Fork 38.5k
AspectJ @annotation
is not working after upgrade from 6.0.23 to 6.2.6
#34894
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
Comments
@annotation
is not working after upgrade from 6.0.23 to 6.2.6
Could you please provide your case with more details because mine is working without any problem, or I simply missed something. Thank you! |
Hi @AmuthaKondusamy, Congratulations on submitting your first issue for the Spring Framework! 👍 Unfortunately, a description of the problem is not enough to go on. As @Emil-Stampfly-He pointed out, if you would like for us to investigate this, please provide a minimal sample application which demonstrates what worked with Spring Framework 6.0.23 and no longer works with Spring Framework 6.2.x. The sample application can be a ZIP file attached to this issue or a public Git repository -- for example, a Spring Boot application created via https://start.spring.io. Thanks |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Uh oh!
There was an error while loading. Please reload this page.
Overview
I have a JUnit test which calls a method which in turn uses
@annotation
call to aspect class.This setup is working well in spring 6.0.23 version but not in 6.2.6, as
@annotation
call is not getting triggered and so JUnit test cases are fail for all aspect-related cases.Kindly help to resolve this issue.
Versions Used
Before upgrade
After upgrade
The text was updated successfully, but these errors were encountered: