Consistent line breaks in reference documentation

Author: jhoeller

framework-docs/antora.yml

@@ -6,7 +6,7 @@ nav:
 ext:
   collector:
     run:
-      command: gradlew -q -PbuildSrc.skipTests=true "-Dorg.gradle.jvmargs=-Xmx3g -XX:+HeapDumpOnOutOfMemoryError" :framework-docs:generateAntoraResources
+      command: gradlew -q -PbuildSrc.skipTests=true "-Dorg.gradle.jvmargs=-Xmx3g" :framework-docs:generateAntoraResources
       local: true
     scan:
       dir: ./build/generated-antora-resources

framework-docs/modules/ROOT/pages/core.adoc

@@ -17,14 +17,3 @@ is also provided.
 
 AOT processing can be used to optimize your application ahead-of-time. It is typically
 used for native image deployment using GraalVM.
-
-
-
-
-
-
-
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api.adoc

@@ -6,7 +6,3 @@ The previous chapter described the Spring's support for AOP with @AspectJ and sc
 aspect definitions. In this chapter, we discuss the lower-level Spring AOP APIs. For common
 applications, we recommend the use of Spring AOP with AspectJ pointcuts as described in the
 previous chapter.
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/advice.adoc

@@ -4,7 +4,6 @@
 Now we can examine how Spring AOP handles advice.
 
 
-
 [[aop-api-advice-lifecycle]]
 == Advice Lifecycles
 
@@ -22,14 +21,12 @@ the advice adds state to the proxied object.
 You can use a mix of shared and per-instance advice in the same AOP proxy.
 
 
-
 [[aop-api-advice-types]]
 == Advice Types in Spring
 
 Spring provides several advice types and is extensible to support
 arbitrary advice types. This section describes the basic concepts and standard advice types.
 
-
 [[aop-api-advice-around]]
 === Interception Around Advice
 
@@ -101,7 +98,6 @@ you are likely to want to run the aspect in another AOP framework. Note that poi
 are not currently interoperable between frameworks, and the AOP Alliance does not
 currently define pointcut interfaces.
 
-
 [[aop-api-advice-before]]
 === Before Advice
 
@@ -168,7 +164,6 @@ Kotlin::
 
 TIP: Before advice can be used with any pointcut.
 
-
 [[aop-api-advice-throws]]
 === Throws Advice
 
@@ -297,7 +292,6 @@ exception that is incompatible with the target method's signature!_
 
 TIP: Throws advice can be used with any pointcut.
 
-
 [[aop-api-advice-after-returning]]
 === After Returning Advice
 
@@ -361,7 +355,6 @@ thrown up the interceptor chain instead of the return value.
 
 TIP: After returning advice can be used with any pointcut.
 
-
 [[aop-api-advice-introduction]]
 === Introduction Advice
 
@@ -501,7 +494,6 @@ Java::
 			}
 			return super.invoke(invocation);
 		}
-
 	}
 ----
 
@@ -531,7 +523,6 @@ Kotlin::
 			}
 			return super.invoke(invocation)
 		}
-
 	}
 ----
 ======
@@ -582,8 +573,3 @@ We can apply this advisor programmatically by using the `Advised.addAdvisor()` m
 (the recommended way) in XML configuration, as any other advisor. All proxy creation
 choices discussed below, including "`auto proxy creators,`" correctly handle introductions
 and stateful mixins.
-
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/advised.adoc

@@ -142,7 +142,3 @@ case, the `Advised` `isFrozen()` method returns `true`, and any attempts to modi
 advice through addition or removal results in an `AopConfigException`. The ability
 to freeze the state of an advised object is useful in some cases (for example, to
 prevent calling code removing a security interceptor).
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/advisor.adoc

@@ -14,7 +14,3 @@ It is possible to mix advisor and advice types in Spring in the same AOP proxy.
 example, you could use an interception around advice, throws advice, and before advice in
 one proxy configuration. Spring automatically creates the necessary interceptor
 chain.
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/autoproxy.adoc

@@ -19,14 +19,12 @@ There are two ways to do this:
   auto-proxy creation driven by source-level metadata attributes.
 
 
-
 [[aop-autoproxy-choices]]
 == Auto-proxy Bean Definitions
 
 This section covers the  auto-proxy creators provided by the
 `org.springframework.aop.framework.autoproxy` package.
 
-
 [[aop-api-autoproxy]]
 === `BeanNameAutoProxyCreator`
 
@@ -61,7 +59,6 @@ automatically created by the `BeanNameAutoProxyCreator`. The same advice is appl
 to all matching beans. Note that, if advisors are used (rather than the interceptor in
 the preceding example), the pointcuts may apply differently to different beans.
 
-
 [[aop-api-autoproxy-default]]
 === `DefaultAdvisorAutoProxyCreator`
 
@@ -125,7 +122,3 @@ differently configured, AdvisorAutoProxyCreators in the same factory) and orderi
 Advisors can implement the `org.springframework.core.Ordered` interface to ensure
 correct ordering if this is an issue. The `TransactionAttributeSourceAdvisor` used in the
 preceding example has a configurable order value. The default setting is unordered.
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/concise-proxy.adoc

@@ -65,7 +65,3 @@ that, if you have a (parent) bean definition that you intend to use only as a te
 and this definition specifies a class, you must make sure to set the `abstract`
 attribute to `true`. Otherwise, the application context actually tries to
 pre-instantiate it.
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/pfb.adoc

@@ -14,7 +14,6 @@ the pointcuts, any advice that applies, and their ordering. However, there are s
 options that are preferable if you do not need such control.
 
 
-
 [[aop-pfb-1]]
 == Basics
 
@@ -32,7 +31,6 @@ application objects (besides the target, which should be available in any AOP
 framework), benefiting from all the pluggability provided by Dependency Injection.
 
 
-
 [[aop-pfb-2]]
 == JavaBean Properties
 
@@ -87,7 +85,6 @@ to be applied. You can find an example of using this feature in xref:core/aop-ap
   `false`.
 
 
-
 [[aop-pfb-proxy-types]]
 == JDK- and CGLIB-based proxies
 
@@ -137,7 +134,6 @@ interface that the target class implements to the `proxyInterfaces` property. Ho
 it is significantly less work and less prone to typographical errors.
 
 
-
 [[aop-api-proxying-intf]]
 == Proxying Interfaces
 
@@ -263,7 +259,6 @@ However, there are times when being able to obtain the un-advised target from th
 factory might actually be an advantage (for example, in certain test scenarios).
 
 
-
 [[aop-api-proxying-class]]
 == Proxying Classes
 
@@ -302,7 +297,6 @@ There is little performance difference between CGLIB proxies and dynamic proxies
 Performance should not be a decisive consideration in this case.
 
 
-
 [[aop-global-advisors]]
 == Using "`Global`" Advisors
 
@@ -325,7 +319,3 @@ two global advisors:
 	<bean id="global_debug" class="org.springframework.aop.interceptor.DebugInterceptor"/>
 	<bean id="global_performance" class="org.springframework.aop.interceptor.PerformanceMonitorInterceptor"/>
 ----
-
-
-
-

framework-docs/modules/ROOT/pages/core/aop-api/pointcuts.adoc

@@ -4,7 +4,6 @@
 This section describes how Spring handles the crucial pointcut concept.
 
 
-
 [[aop-api-concepts]]
 == Concepts
 
@@ -69,7 +68,6 @@ TIP: If possible, try to make pointcuts static, allowing the AOP framework to ca
 results of pointcut evaluation when an AOP proxy is created.
 
 
-
 [[aop-api-pointcut-ops]]
 == Operations on Pointcuts
 
@@ -84,7 +82,6 @@ You can compose pointcuts by using the static methods in the
 expressions is usually a simpler approach.
 
 
-
 [[aop-api-pointcuts-aspectj]]
 == AspectJ Expression Pointcuts
 
@@ -95,14 +92,12 @@ uses an AspectJ-supplied library to parse an AspectJ pointcut expression string.
 See the xref:core/aop.adoc[previous chapter] for a discussion of supported AspectJ pointcut primitives.
 
 
-
 [[aop-api-pointcuts-impls]]
 == Convenience Pointcut Implementations
 
 Spring provides several convenient pointcut implementations. You can use some of them
 directly; others are intended to be subclassed in application-specific pointcuts.
 
-
 [[aop-api-pointcuts-static]]
 === Static Pointcuts
 
@@ -146,7 +141,6 @@ You can use `RegexpMethodPointcutAdvisor` with any `Advice` type.
 An important type of static pointcut is a metadata-driven pointcut. This uses the
 values of metadata attributes (typically, source-level metadata).
 
-
 [[aop-api-pointcuts-dynamic]]
 === Dynamic pointcuts
 
@@ -172,7 +166,6 @@ other dynamic pointcuts. In Java 1.4, the cost is about five times that of other
 pointcuts.
 
 
-
 [[aop-api-pointcuts-superclasses]]
 == Pointcut Superclasses
 
@@ -214,7 +207,6 @@ There are also superclasses for dynamic pointcuts.
 You can use custom pointcuts with any advice type.
 
 
-
 [[aop-api-pointcuts-custom]]
 == Custom Pointcuts
 
@@ -225,7 +217,3 @@ expression language, if you can.
 
 NOTE: Later versions of Spring may offer support for "`semantic pointcuts`" as offered by JAC --
 for example, "`all methods that change instance variables in the target object.`"
-
-
-
-