Thomas Keller

Ah, found that too late. Figured out that the existing plugin can eventually be used starting with 0.17.0 and created another PR for it. But I guess going native Gradle...

Shall I rebase to resolve the conflicts? Is there an interest to get this merge-ready?

@Mita1w Rebased, please have a look.

Interesting info, no, I'm working my way through a lot of legacy (build) code, the plugin is still set on the main buildscript class path and applied using the old...

I updated to a much newer version of the plugin, 2.9.1, and the problem seem to be gone there. I couldn't however not find a suitable way to use the...

Gradle allows to configure dependent plug-ins lazily with `project.plugins.withId("plugin.id") {...}`, even when these plug-ins are added through a plugin block, so this shouldn't be a problem. Am 4. Mai 2021...

That would also help for a request of mine - the generation of a Parameters class that lists all used parameters for a specific URL configuration. Like, when you have...

On a related note: One could now say that for Jacoco, instead of specifying ``` version.org.jacoco..org.jacoco.agent=0.8.5 version.org.jacoco..org.jacoco.core=0.8.5 ``` (org.jacoco.core is added as a dependency from another configuration), why not specify...

Also, on a totally unrelated note, I've read that you want to concentrate on refreshVersions and skip the support for buildSrc for now. Is there any helper / tool for...

dependencies-0.5.8