I don't see why this is that important. The issue exists already in the current implementation, so there's no degradation or loss of functionality.
Sure, in an ideal world, you can define version ranges and all that fancy stuff. In the real world however, it'd work the exact same way any app that depends on third party libs does, a note somewhere that says 'this only works on X.Y onwards, except for X.Y.Z which is broken'. The goal isn't to have something perfect, it's to have something thats not as irritatingly broken as the current situation. On Sep 5, 2011, at 7:03 PM, evgenyg wrote: > If Gradle jars are pushed to the Central repo and then every plugin can > choose any Gradle version to depend upon, then there needs to be a way to > make sure the proper Gradle version is used at run-time. > > For example: > * If plugin doesn't specify any requirement then it runs with any Gradle > version. > * If plugin specifies "same version" requirement then it can only be run > with the Gradle version it was compiled with. > * Third option for a plugin is to specify a range of compatible versions. > > It was > http://gradle.1045684.n5.nabble.com/Verifying-Gradle-version-td4675891.html > previously discussed from the build script point of view. But plugins are > in the same situation. > > ----- > Best regards, > > Evgeny > > evgeny-goldin.com > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/gradleApi-with-1-0-0-m4-tp4656647p4772383.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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
