Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin configuration during wrapper task #30908

Open
diareuse opened this issue Oct 15, 2024 · 1 comment
Open

Plugin configuration during wrapper task #30908

diareuse opened this issue Oct 15, 2024 · 1 comment
Labels
a:bug in:wrapper 👋 team-triage Issues that need to be triaged by a specific team

Comments

@diareuse
Copy link

Current Behavior

When running ./gradlew wrapper --gradle-version X.Y.Z, the com.android.internal.version-check plugin checks the current Gradle version against a minimum required version.

If the current Gradle version is below the minimum, the plugin throws an error and prevents the wrapper task from updating the Gradle wrapper.

This behavior is inconsistent with the expected behavior when using the wrapper task to update the Gradle wrapper.

Therefore we believe that the plugins are being configured during the wrapper step, which in turn disallows updating the plugin for Android projects.

Expected Behavior

When running ./gradlew wrapper --gradle-version X.Y.Z, the com.android.internal.version-check plugin should not enforce a minimum Gradle version during startup.

The Gradle wrapper should be allowed to update to the desired version regardless of the current Gradle version.

Context (optional)

https://issuetracker.google.com/issues/372269616

Self-contained Reproducer Project

  1. Sync the project in AS / IJ
  2. Double ctrl and run ./gradlew wrapper --gradle-version 8.10.2

gradle-repro.zip

Gradle version

8.7 / 8.10.2

Build scan URL (optional)

No response

Your Environment (optional)

No response

@abstratt abstratt added in:wrapper 👋 team-triage Issues that need to be triaged by a specific team and removed to-triage labels Oct 15, 2024
@abstratt
Copy link
Member

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug in:wrapper 👋 team-triage Issues that need to be triaged by a specific team
Projects
None yet
Development

No branches or pull requests

3 participants