Daniel Lacasse

The direction you should be looking for is summarized in this sample: https://docs.gradle.org/current/samples/sample_jvm_multi_project_with_code_coverage.html.

Unfortunately, you will need to use the `allprojects` hook to apply the plugin everywhere which is a bit frowned upon but in this case, it's the only way to achieve...

If the plugin still does what is explained in the description of the issue, then it's not safe to close. The plugin will break in future Gradle versions if it's...

Could this be a good candidate to modularize and pull the latest wrapper generation module if connected to the internet? If not, then we can use the current version in...

Unfortunately, this issue is due to a misuse of the Provider API, see https://dl.bintray.com/mmalohlava/gradle-plugins/ and https://bintray.com/mmalohlava/gradle-plugins/visteg#files how some strings are the result of a `Provider#toString()`. We are also see debug...

There is no obvious mistake in the [build script that published 1.0.4](https://github.com/mmalohlava/gradle-visteg/blob/9d6d50bed3480d3be12399dae0b8356fabf3e0e8/build.gradle). It could come from `plugindev` or from the legacy `uploadArchives` task.

We debugged this further and the issue was coming indirectly from `plugindev` plugin which was applying an old bintray plugin that was using an internal API from Java that changed...

See https://github.com/gradle/gradle/issues/9359 for the complete logs to help the investigation.

Modelling the sysroot allow for a better understanding of what the user's intention is and provide good defaults. We want to prefer stronger modelling and understanding than leaving everything to...

We made a [spike recently ](https://github.com/gradle/gradle/tree/am/resolver-spike)around Homebrew (and Linuxbrew) resolution. I think expending the work we did previously to include more search location could be really beneficial in supporting the...