There are a lot of very annoying transitive dependencies that get sucked in
when building against gradleApi().
For example, we end up with log4j-over-slf4j, which is a thin facade for log4j
but does not cover the whole API. So any projects for example that try to
configure log4j directly will fail to compile, even if they declare a
dependency on log4j explicitly due to this extra jar being sucked in. Similarly
for jcl-over-slf4j, and probably a number of other jars that should remain
internal to gradle and are only required at runtime, not compile time (the
commons-* army, for example).
This to me is yet another argument why a provided configuration should be
supported by default!
If I depend on gradleApi(), I'd like to depend only on the API (and
implementation), I do not want my code to start using any of its downstream
dependencies (or even worse, have them taint my existing dependencies). Is
there any way of achieving this right now?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
