Mention fully executable jars in Jersey’s scanning limitations

Closes gh-3413

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -2866,11 +2866,12 @@ endpoints, as shown in the following example:
 	}
 ----
 
-WARNING: Jersey's support for scanning executable archives is rather limited. For
+WARNING: Jersey's support for scanning executable archives is rather limited. For example,
-example, it cannot scan for endpoints in a package found in `WEB-INF/classes` when
+it cannot scan for endpoints in a package found in a <<deployment.adoc#deployment-install,
-running an executable war file. To avoid this limitation, the `packages` method should
+fully executable jar file>> or in `WEB-INF/classes` when running an executable war file.
-not be used, and endpoints should be registered individually by using the `register`
+To avoid this limitation, the `packages` method should not be used, and endpoints should
-method, as shown in the preceding example.
+be registered individually by using the `register` method, as shown in the preceding
+example.
 
 For more advanced customizations, you can also register an arbitrary number of beans that
 implement `ResourceConfigCustomizer`.