chore: upgrade minimum supported Gradle version to 8.4

[tarekoraby]

Close vaadin/platform#5027.

Related to #18367.

[tarekoraby]

I keep forgetting what the +0.0.1 label is supposed to signify. But just to clarify, this change should be in the next Minor (not 24.3)

[github-actions]

Test Results

1 094 files  ± 0  1 094 suites  ±0   1h 17m 34s ⏱️ - 5m 13s
6 868 tests ± 0  6 822 ✅ ± 0  46 💤 ±0  0 ❌ ±0 
7 189 runs   - 30  7 131 ✅  - 30  58 💤 ±0  0 ❌ ±0 

Results for commit 168c317. ± Comparison against base commit 0a99f4a.

♻️ This comment has been updated with latest results.

[mcollovati]

VaadinSmokeTest.pluginShouldFailWithUnsupportedGradleVersion should be updated as well

[tarekoraby]

There is a failure at

flow/flow-plugins/flow-gradle-plugin/src/functionalTest/kotlin/com/vaadin/gradle/MiscSingleModuleTest.kt

Line 31 in 43aab7c

fun testVaadin8VaadinPlatformMPRProject() {

. I don't understand what's wrong nor how to fix it.

[mcollovati]

I don't understand what's wrong nor how to fix it.

The test ensures that gradle plugin works in MPR projects, in combination with the com.devsoap.plugin.vaadin gradle plugin that is for Vaadin 8.
However, the Vaadin 8 compatible plugin is not maintained anymore, and it looks like it cannot run with Gradle 8.

So I think it means that after this upgrade we cannot support gradle anymore in MPR projects (or we need to fork the project and maintain it by our own)

[tarekoraby]

As discussed on Slack, let's not rely on the deprecated com.devsoap.plugin.vaadin. If MPR + Gradle is requested in the future, we can consider re-introducing the support (e.g., by updating com.devsoap.plugin.vaadin).

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[vaadin-bot]

This ticket/PR has been released with Vaadin 24.4.0.