You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That makes the end user use Gradle taken from the Habitat core/gradle package, which is version v5.6.4 (while the latest stable Gradle version now is 7.1). Therefore and according to the Habitat documentation, if I want to use a different Gradle version I would need to create another package with my preferred version, upload it to the Habitat and override scaffolding_gradle_pkg to reference my package.
However, Gradle documentation recommends using the wrapper to run any task, as it already takes care of invoking the proper Gradle version (taken from the cache or downloaded if it's the first run). Therefore, it would be nice to let Gradle take care of this, so Habitat would not need to maintain and install the Gradle package as build dependency.
Instead of using gradle we could use ./gradlew (it would be a requirement for projects who want to use the Gradle scaffolding to have the Gradle wrapper, which is the most common option nowadays).
Another solution is to always preferably run tasks through the Gradle wrapper (run ./gradlew if gradlew file is present in the project), or otherwise invoke gradle taken from Habitat's core/gradle dependency.
The text was updated successfully, but these errors were encountered:
Currently, the Gradle scaffolding is invoking gradle directly here: https://github.com/habitat-sh/core-plans/blob/master/scaffolding-gradle/lib/scaffolding.sh#L121-L133
That makes the end user use Gradle taken from the Habitat
core/gradle
package, which is version v5.6.4 (while the latest stable Gradle version now is 7.1). Therefore and according to the Habitat documentation, if I want to use a different Gradle version I would need to create another package with my preferred version, upload it to the Habitat and overridescaffolding_gradle_pkg
to reference my package.However, Gradle documentation recommends using the wrapper to run any task, as it already takes care of invoking the proper Gradle version (taken from the cache or downloaded if it's the first run). Therefore, it would be nice to let Gradle take care of this, so Habitat would not need to maintain and install the Gradle package as build dependency.
Instead of using
gradle
we could use./gradlew
(it would be a requirement for projects who want to use the Gradle scaffolding to have the Gradle wrapper, which is the most common option nowadays).Another solution is to always preferably run tasks through the Gradle wrapper (run
./gradlew
ifgradlew
file is present in the project), or otherwise invokegradle
taken from Habitat'score/gradle
dependency.The text was updated successfully, but these errors were encountered: