I don't know if I would call it broken. Maybe not the cleanest. And it is definitely out there. Take a look at servlet-api as an example.
Provided also gives you a way of having a non-transitive compile-time conf. This is useful, for example, if your library needs a jar to compile against, but you know that downstream builds won't need it implicitly. For example, for compile-time-only annotation processing. Another use case is for libraries that provide optional services, where each optional service requires runtime support only if it is enabled. The final app build gets to decide which services it will want, and adds the runtime conf on those in its build. This allows the apps to opt-in to these services, instead of the war task's approach of requiring apps to opt-out or suppress dependencies that they don't want. I found the Jira for this: http://issues.gradle.org/browse/GRADLE-784 which I'll add to. -- View this message in context: http://gradle.1045684.n5.nabble.com/Ivy-vs-Gradle-configurations-tp4544242p4557708.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
