Deprecate the 'wrapper-directory' input and recommend 'gradle-executable' instead

Use of a wrapper in a non-standard directory is uncommon, and is effectively handled
by referencing the `gradlew` script as the `gradle-executable`.
This commit is contained in:
Daz DeBoer 2021-07-07 12:45:24 -06:00
parent 41ca2299a5
commit 5423935c9b
No known key found for this signature in database
GPG key ID: DD6B9F0B06683D5D
3 changed files with 17 additions and 14 deletions

View file

@ -60,14 +60,6 @@ If you need to pass environment variables, simply use the GitHub Actions workflo
build-root-directory: some/subdirectory
```
## Use a Gradle wrapper from a different directory
```yaml
- uses: eskatos/gradle-command-action@v1
with:
wrapper-directory: path/to/wrapper-directory
```
## Use a specific `gradle` executable
```yaml
@ -76,6 +68,16 @@ If you need to pass environment variables, simply use the GitHub Actions workflo
gradle-executable: path/to/gradle
```
## Use a Gradle wrapper from a different directory
```yaml
- uses: eskatos/gradle-command-action@v1
with:
gradle-executable: path/to/gradlew
```
NOTE: The `wrapper-directory` input has been deprecated. Use `gradle-executable` instead.
## Setup and use a declared Gradle version
```yaml