I have been going through it trying to understand Gradle and have run into issues.
If that is the case, I recommend opening a feature request or pull request to improve the docs, so that the next reader might have a better experience.
Sometimes the documentation introduces terms without any explanation, for example in Command Line Interface, Project Reporting mentions Task Groups, this hasn’t been described.
But they are described right there, aren’t they?
I mean, you certainly do not describe what a “group” is and that a “task group” is a “group of tasks” seems just too natural to me.
It talks there about
gradle tasks where when you execute it the groups are shown.
It also shows an example of how to list the tasks of a specific group, which should also make it easier to correlate the term to the output.
And it also shows right after that, you can also see the task group in the
help task output for a specific task.
On the ‘links doesn’t exist’ I clicked on a link and got a html 502, I will try to find it again and report as specified.
A 502 can have many reasons, from a bad proxy configuration, over some misconfigured firewall, or unhappy virus scanner, …
Most of these are way before you even hit any Gradle server.
So if you get a 502, just try it again a bit later, or try to find out where the 502 is actually coming from.
Most often this is not caused by Gradle servers.
Using the online version of the manual I can only search within the page so I also have the PDF version in which I can search the whole manual, unfortunately the PDF version does not match the online version. A detailed Index would be useful.
The same as the PDF version should be available as online as Gradle User Manual: Version 8.4. But both have the problem, that some of the single-page pages are not included unfortunately, which is reported at Improvements for the single-page documentation. · Issue #16760 · gradle/gradle · GitHub and hopefully gets fixed some day.
The search box on the online docs in the upper left if you use the
/current/ docs and not a version specific on is usually quite good though to find things that are missing from the single-page version.
Anyway moving on, the next issue is placing resources into non-standard directories within a jar.
Just configure the
jar task as you need it. Or maybe better configure the
processResources task, so that not only the
jar but also other task needing resources finds them where they need to be like the
run task if you use the
application plugin for example.