Tony Robalik

A workaround for this: ```groovy // Workaround for https://github.com/gradle/gradle/issues/25885 // Technically it should be `explodeCodeSourceMain dependsOn generateGrammarSource` and // `explodeCodeSourceTest dependsOn generateTestGrammarSource`, but this module is so // small it...

> the **lack of a clear definition of an artifact ID** +1 on this statement. I use these interfaces a lot, but it is purely based on exploration and finding...

@BraisGabin would you mind contributing a failing test?

Hm let me restate. You really can't contribute a failing test because the plugin wouldn't have any reason to fail in the presence of this unused plugin. So what you...

The issue does indeed go away if `dependency.analysis.autoapply=false` is omitted. It happens because the plugin configures itself for Android projects inside an `afterEvaluate` block. I think this may not be...

I just ran into this with 7.0.0. I wanted to exclude some Kotlin cruft, so I added ```groovy shadowJar.exclude '**/*.kotlin_metadata' ``` and it didn't seem to be doing anything, till...

Thanks for the issue. I think we could support this via an extension with a `Property` that was user-configurable. That would then be piped through to the task that does...

Thanks for the issue.

Thanks for the issue. Could you provide a minimal reproducer?

Thanks for the issue. Would you consider this a bug or a feature request? I'm not sure of the best resolution. The whitespace is only aesthetic. It is quite literally...