Skip to content

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

Closed
AmuthaKondusamy opened this issue May 14, 2025 · 4 comments
Closed
Labels
in: core Issues in core modules (aop, beans, core, context, expression)

Comments

@AmuthaKondusamy
Copy link

AmuthaKondusamy commented May 14, 2025

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

  • aspectjrt, aspectjweaver: 1.8.7
  • spring-aspect, other spring jars: 6.0.23
  • junit-jupiter: 5.11.0

After upgrade

  • aspectjrt, aspectjweaver: 1.9.24
  • spring-aspect, other spring jars: 6.2.6
  • junit-jupiter: 5.12.2
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label May 14, 2025
@jhoeller jhoeller changed the title Aspectj is not working post spring upgrade to 6.2.6 AspectJ @annotation is not working after upgrade from 6.0.23 to 6.2.6 May 14, 2025
@Emil-Stampfly-He
Copy link

Could you please provide your case with more details because mine is working without any problem, or I simply missed something. Thank you!

@sbrannen sbrannen added the in: core Issues in core modules (aop, beans, core, context, expression) label May 23, 2025
@sbrannen
Copy link
Member

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

@sbrannen sbrannen added the status: waiting-for-feedback We need additional information before we can continue label May 23, 2025
@spring-projects-issues
Copy link
Collaborator

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.

@spring-projects-issues spring-projects-issues added the status: feedback-reminder We've sent a reminder that we need additional information before we can continue label May 30, 2025
@spring-projects-issues
Copy link
Collaborator

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.

@spring-projects-issues spring-projects-issues closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2025
@spring-projects-issues spring-projects-issues removed status: waiting-for-feedback We need additional information before we can continue status: feedback-reminder We've sent a reminder that we need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged or decided on labels Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression)
Projects
None yet
Development

No branches or pull requests

4 participants