Best explanation so far. I searched all around the internet about goals phases plugins but never got such crisp and to the point explanation. my search came to an end today. thanks a lot.
Glad you liked it! If you're interested in Maven > Gradle migration this video runs through the process for a Spring Boot project th-cam.com/video/izZ5_plW6tY/w-d-xo.html
The most enlightening realization in my life about Maven was that 'clean' is the name of the lifecycle as well as the plugin as well as the goal in that plugin... To your question: for me running goals directly was often useful for running various ad-hoc tasks against my dev environment i.e. things like DB scripts (Sql Maven plugin, Flyway Maven plugin). It goes against the Maven's philosophy of build automation, however, it was convenient to define such automation tasks in pom.xml, and keep them in one place with the rest of the build logic. And yes, I know that perfect people don't do that. Thanks for the tutorial. Now I'm convinced about Maven and will start writing pom.xml's right away!
I watched multiple videos about plugins and goals in maven but this video is different and actually amazing! thank you so much for this awesome video.
Very good and clear explanation of goals and phases. Thanks.
Best explanation so far. I searched all around the internet about goals phases plugins but never got such crisp and to the point explanation. my search came to an end today. thanks a lot.
OMG, every Maven user should watch this.
Best explanation I found so far, thx!
Best explanation of how the goals, plugins and phases work that i've seen. You should create a video on how to move from Maven to Gradle.
Glad you liked it! If you're interested in Maven > Gradle migration this video runs through the process for a Spring Boot project th-cam.com/video/izZ5_plW6tY/w-d-xo.html
What a beautiful video!
This has so much more info!
Liked and subscribed :)
The most enlightening realization in my life about Maven was that 'clean' is the name of the lifecycle as well as the plugin as well as the goal in that plugin...
To your question: for me running goals directly was often useful for running various ad-hoc tasks against my dev environment i.e. things like DB scripts (Sql Maven plugin, Flyway Maven plugin). It goes against the Maven's philosophy of build automation, however, it was convenient to define such automation tasks in pom.xml, and keep them in one place with the rest of the build logic. And yes, I know that perfect people don't do that.
Thanks for the tutorial. Now I'm convinced about Maven and will start writing pom.xml's right away!
Great explanation. Nice job!
this is goal!!, thank you
really good explanation. thanks
Really well explained dude thanks
Great explanation
fantastic 😍