The central concept of Gradle is the "Task" - that's where the work is done.

I talked about tasks before: How they are lined up in a task graph, how you configure them, how you register new tasks or implement your own.

Each task implementation has two aspects: (1) What can be configured? (2) What does it do in the so-called Task Actions?

Lets take a closer look at (2) in this new episode:

https://www.youtube.com/watch?v=7ueAnM7ADm4&list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE

#Gradle #Java #UnderstandingGradle

Gradle's CopySpec is flexible and powerful mechanism to copy or package files your build produces. If used smartly, it integrates well with all other parts of the build and allows you to put build results into whatever structure you need them (while sticking to standard conventions everywhere else).

If you work with Gradle, it's worth to take a moment to look at this concept a bit more closely:

https://www.youtube.com/watch?v=LhVhC86FVIY

#Gradle #Java #UnderstandingGradle

org.gradle.api.provider.Property<>

org.gradle.api.provider.Provider<>

These concepts changed how #Gradle projects (should) look today.

I talk about why they were introduced and when/how you work with them.

#UnderstandingGradle

https://www.youtube.com/watch?v=n8Tgr4aLB18&list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE

The dependency resolution of #gradle helps to avoid conflicts on the classpath (which #java alone won't).

❓ When does a conflict occur?
❗ How/why can Gradle resolve it?
😕 How to find undetected conflicts?
💡 What to do about those?

More on #java #modularity in my new
#understandinggradle video:

https://www.youtube.com/watch?v=KocTqF0hO_8&list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE

More on #java #modularity with #gradle

Are there unused (or too much) Jars on your compile classpaths? Do you even know?

Check out my latest video to learn how to use the Dependency Analysis Plugin by @autonomousapps to clean up your compile classpaths and keep them in shape.

https://www.youtube.com/watch?v=Lipf5piizZc&list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE

#understandinggradle

When it comes to modularization, tools like #gradle build on top of what #java supports and provides. I often see confusion about where the functionality of Java tools end and where Gradle starts (and why or why not you need it at all).

That's why I'll do a couple of videos to explore this step-by-step. Here is the first one, in which I talk about the #classpath:

https://www.youtube.com/watch?v=HqAp9JBl2_U&list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE

#understandinggradle