Dependency submission action should handle non-executable `gradlew` script

[yamin8000]

Dependency submission action should handle non-executable `gradlew` script

[bigdaz]

If you build from the command-line, you will execute ./gradlew build. This requires the executable bit to be set on the script.

If you are only building from the IDE, then you may never notice this being broken.

I've pushed a fix for this issue, so with the next release you'll just see a warning in your workflow run, not an error.

[bigdaz]

When I clone your repository, the gradlew script isn't executable, as mentioned in the error. This means that either:

• The IDE you used to generate the project didn't make this file executable, OR
• The executable bit wasn't retained when you committed the project to GitHub

I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable gradlew script, even if it makes no sense to have a project like that.

[yamin8000]

When I clone your repository, the gradlew script isn't executable, as mentioned in the error. This means that either:

* The IDE you used to generate the project didn't make this file executable, OR

* The executable bit wasn't retained when you committed the project to GitHub

I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable gradlew script, even if it makes no sense to have a project like that.

Thanks.

[yamin8000]

When I clone your repository, the gradlew script isn't executable, as mentioned in the error. This means that either:

* The IDE you used to generate the project didn't make this file executable, OR

* The executable bit wasn't retained when you committed the project to GitHub

I think the error message is pretty clear, but the I think the action could be improved to handle a non-executable gradlew script, even if it makes no sense to have a project like that.

I don't know about that, however, somehow changing my workflow file to this fixed the problem. Modern Android apps need JDK 17 but I don't know why we need to grant permission for the gradlew file explicitly.

name: Dependency Submission

on: [ push ]

permissions:
  contents: write

jobs:
  dependency-submission:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout sources
        uses: actions/checkout@v4
      - name: Set up JDK 17
        uses: actions/setup-java@v4
        with:
          java-version: '17'
          distribution: 'temurin'
          cache: gradle
      - name: Grant execute permission for gradlew
        run: chmod +x gradlew
      - name: Generate and submit dependency graph
        uses: gradle/actions/dependency-submission@v3