Great points, Luke. One thing I would add is: For a user that keeps upgrading to latest&gratest Gradle every couple of weeks, fixing the deprecation warnings immediately might be somewhat undesired. I found myself many times fixing the deprecation warnings eagerly. Then, few days later I had to use the older Gradle version, even for a quick check what was the previous behavior. However that wasn't easy any more, because I had to revert my deprecation fixes. Not saying that this is a huge problem but personally I'd like to see some more smartness in the way deprecation warnings are triggered.
In general I'm a great fan of backwards compatibility and keeping deprecated API longer :) (unless we're talking about some evidently wrong or harmful API). > This (location information in deprecation warnings) is already on the todo > list. > Including the plugin name? That's cool. > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito
