I agree with Thibault, *compileOnly* and *provided* have specific
objectives.
Besides you can always tell Gradle to force a specific version of a given
module
https://docs.gradle.org/current/userguide/dependency_management.html#sec:finetuning_the_dependency_resolution_process
2017-04-22 2:48 GMT+
You do not really offer 'more control' that way, as build systems
today already offer full control over transitive dependencies.
Instead, what you do is to force users to handle transitive
dependencies to groovy in an explicit way (unless they happen to have
a groovy version from somewhere else), p
On 16.04.2017 23:38, Schalk Cronjé wrote:
[...]
dependencies {
compileOnly 'org.codehaus.groovy:groovy-all:2.4.7'
}
This obviously means that the consumer of one of my Groovy libraries has
to explicitly state which version of Groovy they require, but IMO it is
better that way as
I am wondering what people's approach is to build Groovy libraries with
Gradle. Most people will probably use something like
dependencies {
compile 'org.codehaus.groovy:groovy-all:2.4.7'
}
which will set the appropriate Groovy version as a dependency. This can
obvisously lead to
