Closed github-actions[bot] closed 1 year ago
Assumed fixed: https://youtrack.jetbrains.com/issue/IDEA-320266/Gradle-Tooling-integration-should-not-use-Gradle-conventions
Same as 02
Fixed, will make a PR with the fix
You may need to update the android plugin in the sample.
You may need to update the android plugin in the sample.
Solved by #76
The Project.getConvention() method has been deprecated. This is scheduled to be removed in Gradle 9.0. Consult the upgrading guide for further information: https://docs.gradle.org/8.3-20230628222425+0000/userguide/upgrading_version_8.html#deprecated_access_to_conventions
Requested clarification, as seems not fixed for me: https://youtrack.jetbrains.com/issue/IDEA-320266/Gradle-Tooling-integration-should-not-use-Gradle-conventions#focus=Comments-27-7637276.0-0
Test Plan
1. Set up local test environment
for sample in $(ls | grep -e '^[0-9][0-9].*'); do cd $sample; ./gradlew wrapper --gradle-version nightly; cd -; done
git clean -fdx
to remove build artifacts from all sample projectsANDROID_HOME
environment variable is properly set on you machine2. Document components
3. Verify scenarios
These scenarios are automatically generated from the lines starting with
TODO (scenario)
in the build script and code files.The sample projects are located in the numbered folders in the repository root. For each project, follow the steps below:
In case of a failure:
// Known issue: https://youtrack.jetbrains.com/issue/IDEA-123456
Scenarios in
build-src
Scenarios in
included-build-src
Scenarios in
multiproject
Scenarios in
java-build-src
Scenarios in
version-catalog-build-src
Scenarios in
error-in-build-script
4. Finalize
Known issue
reference from the sources.new-regresssion-reported
label if you reported something to JetBrains