From b51a14ff92ac1a8053b57f4fe53dcab9e04f1241 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Simon=20Basl=C3=A9?= Date: Thu, 15 Dec 2022 15:01:55 +0100 Subject: [PATCH] Remove statement that users could be on Java < 5 Closes gh-29694 --- framework-docs/src/docs/asciidoc/core/core-aop.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/framework-docs/src/docs/asciidoc/core/core-aop.adoc b/framework-docs/src/docs/asciidoc/core/core-aop.adoc index 61d2135f7a..fc2dea6749 100644 --- a/framework-docs/src/docs/asciidoc/core/core-aop.adoc +++ b/framework-docs/src/docs/asciidoc/core/core-aop.adoc @@ -2920,8 +2920,7 @@ AspectJ. You also need to use AspectJ if you wish to advise join points other th simple method executions (for example, field get or set join points and so on). When you use AspectJ, you have the choice of the AspectJ language syntax (also known as -the "`code style`") or the @AspectJ annotation style. Clearly, if you do not use Java -5+, the choice has been made for you: Use the code style. If aspects play a large +the "`code style`") or the @AspectJ annotation style. If aspects play a large role in your design, and you are able to use the https://www.eclipse.org/ajdt/[AspectJ Development Tools (AJDT)] plugin for Eclipse, the AspectJ language syntax is the preferred option. It is cleaner and simpler because the language was purposefully