Maven Part 1

Hey Readers, let's understand more about the Maven today!

What is Maven?

Let's understand why we use the Maven. As DevOps Engineer we usually take code from version control and deploy it dev/test or production server.

Now how do we deploy it dev/test or production server - copy the code and run it, nope, and never? Using the Build Package.

Oh, what's this Build Package?

Basically, Build Package means starting with source files produced by developers and ending with things like installation packages that are ready for deployment.

Each programming language has its own build tool:

  1. Java - Ant/Maven/Gradle

  2. .Net - Nant/MS Build

  3. Ruby - Rake

  4. Python - PyBuilder

  5. Docker - Docker Images

So far we understood what is Build Tool and Build Package. Now let's understand What is Maven?

Maven is an open source, Java Based, Build Tool. Founded by Apache Tomcat.

Let's understand the execution flow of Java Code:

Helloworld.java - Source Code
javac Helloworld.java- Compile the Java Code
Helloworld. class - Byte Code JVM will understand.

Java Helloworld - To run the Java application.

Using Java we can develop the below application:

  1. Standalone Applications - jar - Java Archive

  2. Web Applications - war (Java Code + web content).

  3. Enterprise Application - ear - enterprise archive. Enterprise Applications contain different modules. To create ear files at least there should be one war file.

Out of this Java Application bigger package would be ear.

Please follow me for more information about the DevOps Topic and tools with detailed examples and usage.

If you have any feedback, you can send it to .