+1 for googling and stack overflow. I'm pretty dumb and the official Gradle documentation just doesn't seem to ever get me where I need to go. Not to mention there are certain "best practices" that have changed over time as Gradle has grown (e.g. 'compile' vs 'implementation').
I mainly just try to figure out how to do something once and keep it in a public repo so I can use it as reference in the future. I absolutely dread having to figure out how to do a new feature or build step every time.
One last thing I found somewhat useful is just going onto GitHub and searching for an existing gradle repo.
For example, I would make a search like 'gradle codenarc', set language to 'Groovy', and sort by date descending. This definitely doesn't work most of the time, but sometimes you'll find the magic repository that already did the hard work. This method also depends on how popular your dependency is.
+1 for googling and stack overflow. I'm pretty dumb and the official Gradle documentation just doesn't seem to ever get me where I need to go. Not to mention there are certain "best practices" that have changed over time as Gradle has grown (e.g. 'compile' vs 'implementation').
I mainly just try to figure out how to do something once and keep it in a public repo so I can use it as reference in the future. I absolutely dread having to figure out how to do a new feature or build step every time.
One last thing I found somewhat useful is just going onto GitHub and searching for an existing gradle repo.
For example, I would make a search like 'gradle codenarc', set language to 'Groovy', and sort by date descending. This definitely doesn't work most of the time, but sometimes you'll find the magic repository that already did the hard work. This method also depends on how popular your dependency is.
Interesting approach to use the GitHub projects as a template (if it fits)