Thanks for the suggestion! I would love to do this but unfortunately it would break compatibility with Gradle 4.
The Gradle devs are pretty aggressive with their deprecations, it is pretty much unavoidable to have a few of them when trying to support a range of Gradle versions. For now I see making this plugin unusable with Gradle 4 is too high a price for "just" fixing a warning.
Thanks for the suggestion! I would love to do this but unfortunately it would break compatibility with Gradle 4.
The Gradle devs are pretty aggressive with their deprecations, it is pretty much unavoidable to have a few of them when trying to support a range of Gradle versions. For now I see making this plugin unusable with Gradle 4 is too high a price for "just" fixing a warning.