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

Backport much of master to 1.9.x; KotlinCompile type, osdetector, lazy buildDir #678

Merged
merged 6 commits into from
Feb 10, 2023

Conversation

ejona86
Copy link
Collaborator

@ejona86 ejona86 commented Feb 10, 2023

This backports #655, #657, #664, #665, #676, #677

ejona86 and others added 6 commits February 10, 2023 10:21
Generally on my laptop I cannot run many of the tests before they fail
with out-of-memory. With this, I can run all the tests successfully.

There does not seem to be a way to request forking directly. Instead,
the docs warn about passing an environment because it will cause
forking. In our case, that seems to be exactly what we want.

I believe this is a workaround and only benefitting indirectly, but it
works and is easy and I'll take what I can get.
* Use KotlinCompile type directly

* Add Kotlin 1.7.20, Gradle 7.6 versions to tests

* Fix codenarc issues

* Do not run all gradleVersion * kotlinVersion combinations

* Bump kotlin and agp versions
kotlin.bintray.com is dead and has an invalid certificate.
repo.gradle.org was for gradle-kotlin-dsl which we're getting through
plugins.gradle.org.
This causes the plugin to use the correct configuration when users
use a non-default buildDir.

Note that for IDEs we create directories in afterEvaluate{}. It is
possible for the user's own afterEvaluate{} to change buildDir. In that
case, the task will output to the 'correct' directory but the mkdirs for
IDEs can be the 'old' buildDir. But users shouldn't be using
afterEvaluate{}, so we don't care and there's no real fix anyway.

Fixes google#674
@ejona86 ejona86 merged commit fd0664d into google:v1.9.x Feb 10, 2023
@ejona86 ejona86 deleted the backport-to-1.9.x branch February 10, 2023 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants