[GRADLE-1163] Clearer documentation Created: 01/Oct/10 Updated: 10/Feb/17 Resolved: 10/Feb/17
As requested by Adam, here are some suggestions for improving the documentation. Note that my perspective is that of a complete newbie, I'm very proficient in Java and Ant, somewhat familiar with maven, and fairly ignorant of both Groovy and Gradle. I'm approaching Gradle as someone who wants a better build than Ant (with a view to migrating a fairly large build script), but doesn't really care about Groovy.
First of all, the build script basics views defining tasks as the most basic thing you could do. I would argue that defining tasks is in fact a fairly advanced usage, and that if gradle does what it says on the tin, is unlikely to be needed for anyone doing standard stuff like compiling some sources and building a file to deploy (war/ear/etc). I'd rename that whole section to a separate document like 'tasks basic guide'.
Going over the Java quickstart next, here are some assumptions that the doc makes that looked like 'magic' to me:
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.