Deprecated documentation has far more content than replacement


(Joe Gamache) #1

I know this will sound silly, but while gradle rocks, it’s usefulness is often only as good as the documentation.

So when you deprecate a method, you MUST make the replaced method have better documentation. A case in point: http://www.gradle.org/docs/current/javadoc/org/gradle/api/artifacts/dsl/RepositoryHandler.html

See the “mavenRepo” method documentation. It tells users how to add multiple maven repositories, gives examples. Basically it is really good!

Next look at the “maven” method documentation. It says VERY little more than what the method name already tells me! If 2.0 removes the deprecated methods, this info will be lost…

PLEASE FIX THIS AS A HIGH PRIORITY - it really affects the installed base!

thanks!