Skip to main content

๐Ÿš€ Maven vs Gradle – The Complete Dependency & Packaging Guide

๐Ÿš€ Maven vs Gradle – The Complete Dependency & Packaging Guide

As developers, we all have faced this moment ๐Ÿ‘‰ "Why my JAR is not running? Where did my dependency go?" ๐Ÿ˜‚
Let’s break down Maven vs Gradle concepts in a fun, colorful, and interview-friendly way.


๐Ÿ”Œ 1. What is a Plugin & Why Do We Need It?

๐Ÿ‘‰ Plugin = Tool that adds extra power to your build system.
Without plugins, Maven/Gradle can’t compile, test, or package.

  • Maven: Uses <plugin> inside pom.xml. Example: maven-compiler-plugin, spring-boot-maven-plugin.
  • Gradle: Uses plugins { } block. Example: id 'java', id 'org.springframework.boot'.

๐Ÿ˜… Without Plugins?
Your project is like Iron Man without his suit — just a normal guy!

<!-- Maven Example -->

<plugin>

  <groupId>org.apache.maven.plugins</groupId>

  <artifactId>maven-compiler-plugin</artifactId>

  <version>3.11.0</version>

  <configuration>

    <source>17</source>

    <target>17</target>

  </configuration>

</plugin>

// Gradle Example

plugins {

    id 'java'

    id 'org.springframework.boot' version '3.3.0'

}


๐Ÿ“ฆ 2. BOM Imports

BOM = Bill of Materials = Dependency version manager.
It avoids version conflicts (a.k.a. "Jar Hell" ๐Ÿ”ฅ).

  • Maven: Uses <dependencyManagement> with import scope.
  • Gradle: Uses platform() or bomImports.
<!-- Maven Example -->

<dependencyManagement>

  <dependencies>

    <dependency>

      <groupId>org.springframework.boot</groupId>

      <artifactId>spring-boot-dependencies</artifactId>

      <version>3.3.0</version>

      <type>pom</type>

      <scope>import</scope>

    </dependency>

  </dependencies>

</dependencyManagement>

// Gradle Example

dependencies {

    implementation platform("org.springframework.boot:spring-boot-dependencies:3.3.0")

    implementation "org.springframework.boot:spring-boot-starter-web"

}

๐Ÿ’ก Real Time: Spring Boot uses BOM to keep web, security, data-jpa jars aligned in versions.


๐Ÿ› ️ 3. Dependency Scopes

Gradle Scopes:

  • implementation → Used in main code & exported in JAR.
  • testImplementation → Only for tests (JUnit, Mockito).
  • compileOnly → Available at compile-time but NOT in JAR.
  • annotationProcessor → Special for tools like Lombok, MapStruct.

Maven Scopes:

  • compile (default) → Like Gradle implementation.
  • test → Like Gradle testImplementation.
  • provided → Like Gradle compileOnly.
  • system → Rare, local JAR.

๐Ÿ’ก Lombok Example:

<!-- Maven -->

<dependency>

  <groupId>org.projectlombok</groupId>

  <artifactId>lombok</artifactId>

  <version>1.18.30</version>

  <scope>provided</scope>

</dependency>

// Gradle

dependencies {

    compileOnly "org.projectlombok:lombok:1.18.30"

    annotationProcessor "org.projectlombok:lombok:1.18.30"

}

๐Ÿ‘‰ Why both?
compileOnly → So IDE/compiler knows about @Getter, @Builder.
annotationProcessor → So Lombok generates bytecode during build.


๐Ÿฅค 4. Flat JAR vs Fat JAR vs Boot JAR

  • Flat JAR → Only your code, no dependencies. (Normal library JAR).
  • Fat JAR → Your code + all dependencies bundled together.
  • Boot JAR → Spring Boot style fat JAR with embedded Tomcat/Jetty.

๐Ÿ’ก Real Example:
- Common library for microservices → Flat JAR.
- Final microservice → Boot JAR (so it can run java -jar directly).


๐Ÿƒ 5. Special Case: MongoDB Example

Suppose your common library uses MongoDB driver, but not all microservices need it.
Solution ๐Ÿ‘‰ Don’t package Mongo inside the library JAR. Instead:

  • Mark Mongo as provided (Maven) / compileOnly (Gradle).
  • The actual microservice decides whether to include it or not.
<!-- Maven Common Library -->

<dependency>

  <groupId>org.mongodb</groupId>

  <artifactId>mongodb-driver-sync</artifactId>

  <version>4.11.0</version>

  <scope>provided</scope>

</dependency>


๐Ÿ“ฆ 6. Default Packaging Type

  • Maven → Default jar (unless specified as pom or war).
  • Gradle → Default is also jar for java plugin, bootJar if Spring Boot plugin applied.

๐ŸŽฏ Interview Questions

  1. What’s the difference between implementation and compileOnly in Gradle?
  2. How does Maven’s provided compare to Gradle’s compileOnly?
  3. Why do we need both compileOnly and annotationProcessor for Lombok?
  4. What is a BOM and why is it needed?
  5. Flat JAR vs Fat JAR vs Boot JAR → which one for common libraries?
  6. What is Maven’s default packaging type?
  7. Without plugins, can Maven/Gradle build projects?

๐ŸŽ Wrapping Up

So next time someone asks: ๐Ÿ‘‰ "Why do we need BOMs, plugins, or scopes?" You can confidently say: "Because without them, our build is like a pizza without cheese!" ๐Ÿ•๐Ÿ˜‚

Comments

Popular posts from this blog

๐Ÿ” Is final Really Final in Java? The Truth May Surprise You ๐Ÿ˜ฒ

๐Ÿ’ฌ “When I was exploring what to do and what not to do in Java, one small keyword caught my eye — final . I thought it meant: locked, sealed, frozen — like my fridge when I forget to defrost it.”   But guess what? Java has its own meaning of final… and it’s not always what you expect! ๐Ÿ˜… Let’s break it down together — with code, questions, confusion, jokes, and everything in between. ๐ŸŽฏ The Confusing Case: You Said It's Final... Then It Changed?! ๐Ÿซ  final List<String> names = new ArrayList <>(); names.add( "Anand" ); names.add( "Rahul" ); System.out.println(names); // [Anand, Rahul] ๐Ÿคฏ Hold on... that’s final , right?! So how on earth is it still changing ? Time to dive deeper... ๐Ÿง  Why Is It Designed Like This? Here’s the key secret: In Java, final applies to the reference , not the object it points to . Let’s decode this like a spy mission ๐Ÿ•ต️‍♂️: Imagine This: final List<String> names = new ArrayList <>(); Be...

๐ŸŒŸ My Journey – From Zero to Senior Java Tech Lead ๐ŸŒŸ

 There’s one thing I truly believe… If I can become a Java developer, then anyone in the world can. ๐Ÿ’ฏ Sounds crazy? Let me take you back. ๐Ÿ•“ Back in 2015… I had zero coding knowledge . Not just that — I had no interest in coding either. But life has its own plans. In 2016, I got a chance to move to Bangalore and joined a Java course at a training center. That’s where it all started — Every day, every session made me feel like: "Ohhh! Even I can be a developer!" That course didn’t just teach Java — it gave me confidence . ๐Ÿงช Two Life-Changing Incidents 1️⃣ The Interview That Wasn't Planned Halfway through my course, I had to urgently travel to Chennai to donate blood to a family member. After that emotional rollercoaster, I found myself reflecting on my skills and the future. The next day, as I was preparing for my move to Bangalore to complete the remaining four months of my course, I randomly thought — "Let me test my skills... let me just see...

๐ŸŽข Java Loops: Fun, Fear, and ForEach() Fails

๐ŸŒ€ Oops, I Looped It Again! — The Ultimate Java Loop Guide You Won't Forget “I remember this question from one of my early interviews — I was just 2 years into Java and the interviewer asked, ‘Which loop do you prefer and why?’” At first, I thought, “Duh! for-each is cleaner.” But then he grilled me with cases where it fails. ๐Ÿ˜ต That led me to explore all loop types, their powers, and their pitfalls. Let’s deep-dive into every major Java loop with examples &  real-world guidance so you'll never forget again. ๐Ÿ” Loop Type #1: Classic For Loop — “The Old Reliable” ✅ When to Use: You need an index You want to iterate in reverse You want full control over loop mechanics ✅ Good Example: List<String> names = List.of("A", "B", "C"); for (int i = 0; i < names.size(); i++) { System.out.println(i + ": " + names.get(i)); } ๐Ÿ”ฅ Reverse + Removal Example: List<String> item...