►► Getting started with Gradle just got much easier. Check out my FREE Get Going with Gradle course → learn.tomgregory.com/courses/get-going-with-gradle
It took me a whole while to actually understand the older ones, but only after a short while, Gradle changed into implementation and api. However, the older ones (Maven conventions) are more straight-forward right? We used to have compile - For compile & runtime classpaths provided - For compile classpath but not runtime classpath runtime - For only runtime classpath After spending so much time to understand the above and seeing Gradle changed them immediately later, made me stick to implementation which simply worked everywhere I go. Thanks for this video, I finally understand the new approach too.
Excellent video, really well covered. Again how a friendly suggestion: consider to do a new video of this same type but covering about Testing. There are other 'names' about how to refer the dependencies. Keep doing this amazing work!
It would be nice to talk to the rest of the world learning the tools who haven't been using them for 1+ years. You should start by giving a reference to build on. Visualize your reference. Thanks for the effort. Now I need to go to a source that can get me up to speed to understand what you're saying.
Awesome! This is what I am looking for a visual representation of what is happening behind the scene. One more question, what will happen if I change jackson from api to implementation in consumer side
Excellent video :-). can I transform the library module to be used as a BOM into de Consumer? If yes, should I include a pom that list all my libs into my Library module?
Annotation processors generate additional code. Any consumers of your library don't need to know about the annotation processor, so there's no api equivalent to the annotationProcessor configuration.
@@TomGregoryTech thank you. So if I have lombok annotationprocessor in parent library it will not be visible as transitive dependency to consumers of library? I need to have lombok annotationprocessor declared under dependencies for each child project?
►► Getting started with Gradle just got much easier. Check out my FREE Get Going with Gradle course → learn.tomgregory.com/courses/get-going-with-gradle
I spent hours of research and couldn't understand until i found this video. Thank you so much
didn't quite get this before your explanation.. the way you showed the published maven pom artifact lit the light bulb in my thick head ;^) thnx !
Your Gradle series is brilliant. Thank you, Tom.
It took me a whole while to actually understand the older ones, but only after a short while, Gradle changed into implementation and api. However, the older ones (Maven conventions) are more straight-forward right?
We used to have
compile - For compile & runtime classpaths
provided - For compile classpath but not runtime classpath
runtime - For only runtime classpath
After spending so much time to understand the above and seeing Gradle changed them immediately later, made me stick to implementation which simply worked everywhere I go. Thanks for this video, I finally understand the new approach too.
Excellent video, really well covered. Again how a friendly suggestion: consider to do a new video of this same type but covering about Testing. There are other 'names' about how to refer the dependencies. Keep doing this amazing work!
Thank for example about plugin "maven-publish". It's very helpful
thank you for great explanation. So basic, so clear and yet, detailed enough to generate and use library.
Awesome, glad it helped!
Excellent explanation, to the point.
Thank you so much.
Glad it was helpful!
Great explanation! Thank you!
the gradle GOAT
It would be nice to talk to the rest of the world learning the tools who haven't been using them for 1+ years. You should start by giving a reference to build on. Visualize your reference. Thanks for the effort. Now I need to go to a source that can get me up to speed to understand what you're saying.
Hi Tony. Thanks for the suggestion. I will definitely keep this in mind for future tutorials. What specifically did I miss out of this one?
Good demonstration!
Hi, very good demonstration! It would be nice if you can demonstrate compileOnly, runtimeOnly and annotationProcessor :)
Thanks Konrad! That's a great suggestion, and I've added to the list of future topics to cover.
Awesome! This is what I am looking for a visual representation of what is happening behind the scene.
One more question, what will happen if I change jackson from api to implementation in consumer side
Brilliant video thanks
Happy to help Danny
Excellent video :-). can I transform the library module to be used as a BOM into de Consumer? If yes, should I include a pom that list all my libs into my Library module?
Hi Alexandre. That's not something I've tried before unfortunately. Thanks for the feedback.
The jacket in the background disturb me a lot :)
Amazing
Awesome video thank you. Do you have anything planned about how to handle non jar dependencies from zip files like dlls/js/.. ?
Thank you. Sorry, no plans to cover that topic at the moment.
What the equivalent to dependency management in maven to gradle?
What is the api equivalent for annotationprocessor for lombok
Annotation processors generate additional code. Any consumers of your library don't need to know about the annotation processor, so there's no api equivalent to the annotationProcessor configuration.
@@TomGregoryTech thank you. So if I have lombok annotationprocessor in parent library it will not be visible as transitive dependency to consumers of library? I need to have lombok annotationprocessor declared under dependencies for each child project?
@@praveenathangavel That's right. If the subproject requires annotation processing, you need to declare the Lombok annotation processor.
Your IntelliJ IDEA Theme doesn't correlate with your room and t-shirt Theme. Please make it IntelliJ Light as well :-)
Application Binary Interface
Cannot access com.fasterxml.jackson.databind.JsonNode =>
IntelijIdea, but in eclipse ok ... why?