Fix vaadin version not appearing in the gradle config doc

Author: HerbertsVaadin

articles/flow/configuration/gradle.adoc

@@ -6,6 +6,8 @@ meta-description: Learn how to set up and use Gradle for building and managing V
 order: 131
 ---
 
+include::{articles}/_vaadin-version.adoc[]
+
 = Gradle Configuration Properties
 
 --
@@ -21,23 +23,23 @@ For information about using Gradle, see the link:https://docs.gradle.org/current
 
 .Requirements
 [NOTE]
-The Vaadin Gradle plugin requires Java SDK 17 or later, Gradle 8.5 or later.
-It will install Node.js and npm automatically when running the build for the first time.
+The Vaadin Gradle plugin requires Java SDK 17 or later, Gradle 8.7 or later.
+It will install Node.js and npm automatically when running the build for the first time if they are missing or the installed version is below the minimum required.
 If you plan to use Vaadin's Gradle-based starter projects, there's no need to install Gradle on your machine. A Gradle Wrapper script is included in starter projects. It manages locally the download and execution of Gradle for your project. For more information on using Gradle Wrapper, see the https://docs.gradle.org/current/userguide/gradle_wrapper.html[Official Gradle Documentation].
 
 
 [[build-file.vaadin-options]]
 === Vaadin Plugin Configuration
 
-Vaadin Gradle plugin options are configured in a `vaadin` block. For development, the block is usually like this:
+Vaadin Gradle plugin options are configured in a `vaadin` block. An example configuration could be like this:
 
 ----
 vaadin {
-    optimizeBundle = false
+    frontendHotdeploy = true
 }
 ----
 
-If the parameter is `true`, the frontend bundle is optimized for all supported browsers, but the compilation is much slower. For configuration options, see <<all-options,plugin configuration options>>
+If the parameter is `true`, it enables development using the frontend development server instead of an application bundle. This applies only to development mode.
 
 
 [[build-file.repositories]]
@@ -48,6 +50,7 @@ The `repositories` section defines the locations to search for packages. The rep
 ----
 repositories {
     mavenCentral()
+    mavenLocal()
     maven { url = "https://maven.vaadin.com/vaadin-addons" }
     maven { url "https://maven.vaadin.com/vaadin-prereleases" }
     maven { url "https://plugins.gradle.org/m2/" }
@@ -57,6 +60,7 @@ repositories {
 The example above shows configured repositories in the following order:
 
  * *Maven central* (required) - contains Vaadin and a lot of other public libraries
+ * *Maven local* - Repository which looks in the local Maven cache for dependencies.
  * repository for *Vaadin add-ons*
  * repository for *Vaadin pre-releases* - not recommended for production environments
  * *Gradle plugin repository* - only necessary when using Gradle community plugins, which are not available through Maven central
@@ -69,21 +73,21 @@ You can use any Gradle repository definitions in the block. See https://docs.gra
 
 You'll need to add the `vaadin-core` or `vaadin` library as a Java dependency. You would do that like so:
 
+[source,subs="+attributes"]
 ----
 dependencies {
-    implementation "com.vaadin:vaadin-core:24.+"
+    implementation "com.vaadin:vaadin-core:{vaadin-version}"
 }
 ----
 
-When you specify a version of `24.+`, you're choosing to use the latest version of Vaadin. However, you can also specify the exact version. See https://docs.gradle.org/current/userguide/declaring_dependencies.html[Declaring Dependencies] in the Gradle documentation for more details.
 
 [[compiling.tasks]]
 === Vaadin Tasks
 
 The Vaadin-related tasks handled by the plugin are as follows:
 
 `vaadinPrepareFrontend`::
-This checks that Node.js and `npm` are installed, copies frontend resources, and creates or updates the [filename]`package.json` and Vite configuration files (i.e., [filename]`vite.config.ts` and [filename]`vite.generated.ts`). The frontend resources are inside `.jar` dependencies: they're copied to `node_modules`.
+This step verifies that Node.js and `npm` are installed, copies the frontend resources, and, if needed, creates or updates the [filename]`package.json` file and Vite configuration files (i.e., [filename]`vite.config.ts` and [filename]`vite.generated.ts`). The frontend resources are located within `.jar` dependencies and are copied to `src/main/frontend/generated/jar-resources`.
 
 `vaadinBuildFrontend`::
 This builds the frontend bundle with the `Vite` utility. Vaadin frontend resources (e.g., HTML, JavaScript, CSS, and images) are bundled to optimize loading the frontend. This task isn't executed automatically on the `build` and other targets, so you'll need to run it, explicitly.

articles/getting-started/start/alternatives/gradle.adoc

@@ -23,7 +23,7 @@ For information about using Gradle, see the link:https://docs.gradle.org/current
 
 .Requirements
 [NOTE]
-The Vaadin Gradle plugin requires Java SDK 17 or later, Gradle 8.5 or later. It will install Node.js and npm automatically when running the build for the first time.
+The Vaadin Gradle plugin requires Java SDK 17 or later, Gradle 8.7 or later. It will install Node.js and npm automatically when running the build for the first time if they are missing or the installed version is below the minimum required.
 If you plan to use Vaadin's Gradle-based starter projects, there's no need to install Gradle on your machine. A Gradle Wrapper script is included in starter projects. It manages locally the download and execution of Gradle for your project. For more information on using Gradle Wrapper, see the https://docs.gradle.org/current/userguide/gradle_wrapper.html[Official Gradle Documentation].