I see it somewhat differently. If someone declares a dependency on a third-party library, it normally gets downloaded by Maven or Ivy (+/- conflicts involved).
If Gradle plugin declares dependency on any specific Gradle version, and marks this dependency as http://issues.gradle.org/browse/GRADLE-784 "provided" then no dependency will be downloaded for it (I suppose nobody wants plugins to pull different Gradle versions from Maven repos when builds start). As a plugin author it will make me very unsure about run-time environment: being dependent on X when the plugin is built but running with God knows what, having no way to verify or enforce it. Correct, this problem already exists today and I all was pointing out is that some kind of Gradle version enforcer will be very helpful (both for build scripts and plugins), especially when or if getting Gradle as a regular dependency will be made easier. ----- Best regards, Evgeny evgeny-goldin.com -- View this message in context: http://gradle.1045684.n5.nabble.com/gradleApi-with-1-0-0-m4-tp4656647p4773783.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
