On gradle 2.4, the following code was expected to exclude the commons-logging jar:
configurations {
// use the one on tomee/lib instead!!!
all*.exclude group: 'commons-logging', module: 'commons-logging'
}
Running with -d, I see lots of statements showing exclusion, such as:
commons-logging:commons-logging is excluded from commons-httpclient:commons-httpclient:3.1(runtime).
However towards the end I see the module gets included anyway:
Attaching commons-logging:commons-logging:1.1(compile) to its parents
...
Found artifact 'commons-logging.jar (commons-logging:commons-logging:1.1)' in resolver cache: ...
Is this a Gradle bug?
Thanks