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
The default clean hook fails for my project. In particular, my project is a Java Gradle project with the Gradle wrapper installed. I also have a local Gradle installation which is a different version than the wrapper. Due to GradleUp/shadow#287 , the project fails when running with the locally installed version of Gradle, but works when the wrapper is used. By default, up is currently using the wrapper for build, but the locally installed Gradle for clean.
Steps to Reproduce
With a project that uses Gradle and has the wrapper installed, run up deploy -v and see that the clean didn't use the Gradle wrapper.
Prerequisites
up upgrade
)-v, --verbose
flag.Description
TLDR: in the
javaGradle
support inruntimes.go
, both the build and clean hooks should check for the availability of the gradle wrapper.See
up/config/runtimes.go
Line 95 in c5f75ff
The default clean hook fails for my project. In particular, my project is a Java Gradle project with the Gradle wrapper installed. I also have a local Gradle installation which is a different version than the wrapper. Due to GradleUp/shadow#287 , the project fails when running with the locally installed version of Gradle, but works when the wrapper is used. By default, up is currently using the wrapper for build, but the locally installed Gradle for clean.
Steps to Reproduce
With a project that uses Gradle and has the wrapper installed, run
up deploy -v
and see that the clean didn't use the Gradle wrapper.Love Up?
Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.
Slack
Join us on Slack https://chat.apex.sh/
The text was updated successfully, but these errors were encountered: