Maven

Table of Contents

Comparison: Maven vs Gradle

  1. Starting out with Gradle may seem easy, but based on previous experiences, using Maven will give us much more flexibility.
  2. When it comes to Maven’s power at confuguring profiles, environment variables, etc. the time spent to learn it once will be a good investment.
  3. For now, I am going to just stick to using maven (and not Gradle) as much as I can. Based on what I have seen so far, Maven is much more powerful and flexible if you invest a little bit of time learning it once.

Reading material:

  1. https://phauer.com/2018/moving-back-from-gradle-to-maven/

Reading material

  1. https://maven.apache.org/guides/
  2. https://www.vogella.com/tutorials/ApacheMaven/article.html#maven-vs-other-build-tools
  3. https://www.baeldung.com/maven-dependency-scopes

KNOWLEDGE GAP - LEARN MORE, IMPLEMENT THIS

How to set-up a common maven configuration with dependencies and plugins (like code formatter and code validator) and use that common configuration in all the rest of the applications?

TODO Take notes from these articles.

Internal references

  1. https://github.com/explorer436/programming-playground/tree/main/java-playground/copy-artifacts-using-maven
  2. https://github.com/explorer436/programming-playground/tree/main/java-playground/openapi-and-swagger

Links to this note