Alex Semin

Emit Java toolchain usage events from a new Provider with a side effect

5

Fixes #21314 Also fixes #21368

TBD

Kotlin Gradle plugin does not emit Java Toolchain usage events when loaded from configuration cache

1

This is most likely happening due to Kotlin plugin extracting values from a `JavaLauncher` and storing them in a custom data structure. https://github.com/JetBrains/kotlin/blob/ca193a89d2d0408d4720a5dceff004af9f539244/libraries/tools/kotlin-gradle-plugin/src/common/kotlin/org/jetbrains/kotlin/gradle/tasks/DefaultKotlinJavaToolchain.kt#L206-L228 Once this is adjusted on the Kotlin...

This does not work only for the case when toolchains are not configured explicitly. When toolchains are configured either via java plugin or directly on the `javadoc` task via the...

We should find a better solution to disposing of `ProjectBuilder` instances in the (integration) tests. Related #21387

The current link seems to pointing to a stale location

TBD Fixes https://github.com/gradle/gradle/issues/21386 TODO: - [ ] Update docs for `JavaToolchainService` - [ ] Add tests that check the override priority for tools (tool property >> executable path / java...

Close all database pools when the app exits

2

Databases are known to be resilient services, however, it does not mean that the database clients should disregard common protocols when interacting with the database. In particular, it is important...

Plugin should close the database connection on exit

2

Currently there is no way of cleanly closing the database connection when the user quits the app. Most databases are resilient to this, but such a behavior can lead to...