IDEA-358562 Suggest migrating existing projects to Daemon JVM criteria #2882
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The
Daemon toolchain
was introduced in Gradle 8.8 and the motivation behind it and other technical details can be found on the public spec document. The implementation follows the agreed details on spec document and UI/UX document.Summary
This PR creates a info dialog suggesting users to migrate their project to
Daemon JVM criteria
. The migration process will take into consideration the existingGradle JDK configuration
and creating the criteria based on it. In case ofvendor
is important to highlight that must be known by foojay plugin otherwise the download URL are not going to returned for this reason if that's not the case its value will not be specified.NOTE: For now any suggestion to migrate projects will be disabled until Daemon JVM criteria supports the auto-provisioning
Tasks
Tests
Demo
Screen.Recording.2024-11-27.at.10.58.56.mov