docs: update references to allowed and blocked packages (#3191) (#3327)

articles/guide/start/gradle.adoc

@@ -565,7 +565,7 @@ The output directory for generated non-served resources, such as the token file.
 
 When the list of dependencies causes the classpath to go over a set limit on Windows, the build automatically generates a JAR containing a manifest with the classpath. Sometimes, when running a Spring Boot application, the resource loader doesn't load the classpath packages correctly from the manifest. The failed annotation scanning makes the required `npm` packages unavailable.
 
-You can fix this in two ways: add the repository `mavenLocal()` to <<#build-file.repositories,build file repositories>>; or specify the `vaadin.whitelisted-packages` property, see <<../../integrations/spring/configuration#,Vaadin Spring Configuration>>.
+You can fix this in two ways: add the repository `mavenLocal()` to <<#build-file.repositories,build file repositories>>; or specify the `vaadin.allowed-packages` property, see <<../../integrations/spring/configuration#,Vaadin Spring Configuration>>.
 
 
 [discussion-id]`FA18F1BF-2C67-4CCF-85A2-C3E4D7AECFDB`

articles/integrations/spring/configuration.asciidoc

@@ -19,24 +19,27 @@ There are several special configuration parameters for Spring, such as configuri
 
 To decrease the startup time during development, as well as the build time for the production bundle, Vaadin Flow automatically excludes many packages from being scanned for annotations -- such as the ones belonging to the `java` and `springframework` packages. The set of packages that Flow excludes by default are defined in the [classname]`VaadinServletContextInitializer` class.
 
-You can extend this list using the `vaadin.blacklisted-packages` property, which is a comma-separated string that can be used to exclude packages from being scanned. You would do something like the following:
+You can extend this list using the `vaadin.blocked-packages` property, which is a comma-separated string that can be used to exclude packages from being scanned. You would do something like the following:
 
 .application.properties
 [source,properties]
 ----
-vaadin.blacklisted-packages=org/bouncycastle,com/my/db/package
+vaadin.blocked-packages=org/bouncycastle,com/my/db/package
 ----
 
-The `whitelisted-packages` is a comma-separated string that can be used to specify the only packages that need to be scanned for UI components and views. You should set this property to improve performance during development, especially in large applications. The [classname]`com/vaadin/flow/component` package is implicitly included and is always scanned.
+The `allowed-packages` is a comma-separated string that can be used to specify the only packages that need to be scanned for UI components and views. You should set this property to improve performance during development, especially in large applications. The [classname]`com/vaadin/flow/component` package is implicitly included and is always scanned.
 
 .application.properties
 [source,properties]
 ----
-vaadin.whitelisted-packages=com/foo/myapp/ui,com/foo/components
+vaadin.allowed-packages=com/foo/myapp/ui,com/foo/components
 ----
 
 [NOTE]
-You should use either `whitelisted-packages` or `blacklisted-packages` -- not both. If both have values, though, `blacklisted-packages` is ignored.
+You should use either `allowed-packages` or `blocked-packages` -- not both. If both have values, though, `blocked-packages` is ignored.
+
+[IMPORTANT]
+The previous `vaadin.whitelisted-packages` and `vaadin.blacklisted-packages` properties have been deprecated, and will be removed in the future.
 
 
 === Prevent Handling of Specific URLs