Do not depend on dynamic versions

[debanne]

Dynamic versions make the execution of the code that depends on this
plugin less deterministic.

[TheBoegl]

I understand your reasoning, though dependencies on fixed versions of the shadow plugin and log4j-core are not intended because they would limit the usage of this helper class. Both dependencies are declared in the project anyways and, therefore, should be used as intended by the developer.

I should really document the intended use of this class more clearly.

[debanne]

My concern is that Gradle takes the latest version when there is a version conflict. So the dependencies have to be declared with { force = true } to not take the last one:

  dependencies {
      classpath "com.github.jengelman.gradle.plugins:shadow:2.0.1", { force = true }
      classpath 'de.sebastianboegl.gradle.plugins:shadow-log4j-transformer:2.1.1'
   }

Shouldn't this library depend on the first version of shadow it is compatible with (such as 1.0.0 and 2.0.0)? That would avoid the need to use the 'force' property.

[TheBoegl]

I see. I'll accept your PR, document the internal change and publish a new version. Thanks for your PR and help!