John Engelman

I'm pretty sure it works in your repo due to classpath ordering, which isn't really _guaranteed_. Have you tried using any `exclude` configurations to drop the file from log4j?

I actually see this a problem with Nebula's provided plugin. The issue here in my mind is that they are declaring the `provided` configuration as a root of `compile` (https://github.com/nebula-plugins/gradle-extra-configurations-plugin/blob/master/src/main/groovy/nebula/plugin/extraconfigurations/ProvidedBasePlugin.groovy#L60)....

Yeah, actually everything proposed can have issues in some scenarios. Say for example that you have a transitive dependency that gets resolved in both the `provided` and `compile` configurations (assuming...

hmm, yeah...this is going to be a tough one. The problem here is that the contents of the jars themselves aren't actually included in the `source` from the perspective of...

Would be a welcome community contribution.

`mainClassName` isn't an extension property - http://gradle.org/docs/current/userguide/application_plugin.html just set the value directly in `build.gradle` ``` apply plugin: 'application' mainClassName = .... ```

My first thought would be that it should be implemented vi a `Transformer` implementation, but the API doesn't currently pass any information about which archive file the currently processed source...

Happy to incorporate any pull requests that tighten it up. I don't use the Kotlin DSL though, so I'm not likely to do this myself any time soon.

^ again, contributions welcome. I don’t use Kotlin.

Thanks @jbartok. I'm looking at the `java-gradle-plugin` and I'm wondering what the best way for me to implement the functionality [here](https://github.com/gradle/gradle/blob/50e3e8b110da3c5d846abd4d66776ef277d2a940/subprojects/plugin-development/src/main/java/org/gradle/plugin/devel/plugins/JavaGradlePluginPlugin.java#L216-L222) without using internal APIs. Also, it's appears your first...