Ant was the first modern build tool for Java projects, released in 2000. It is easy to use but lacks conventions around project structure and behavior. Maven was released in 2004 to improve on Ant's problems. Maven uses conventions for project structure and a declarative approach, allowing developers to simply define their project in a pom.xml file rather than explicitly specifying each build step.

1. Java Build tools : Ant and Maven
 Ant was the first among “modern” build tools.
 It was released in 2000 and in a short period of time became the most popular build
tool for Java projects.
 It is very easy to learn thus allowing anyone to start using it without any special
preparation.
 It is based on procedural programming idea.
 Maven was released in 2004. Its goal was to improve upon some of the problems
developers were facing when using Ant.
© Sun Technologies Inc. 1

2. © Sun Technologies Inc.
Apache Ant features
2
 Ant doesn’t have formal conventions like a common project directory structure or
default behavior.
 You have to tell Ant exactly where to find the source and where to put the output.
 Ant is procedural.
You have to tell Ant exactly what to do and when to do it.

3. © Sun Technologies Inc.
Getting started with Ant
 Download and unzip the latest version of ANT.
 You should have installed Java and set up path of JAVA_HOME.
 Set PATH environment variable by appending path of ANT.
 Build a basic ANT script and run from command prompt.
3

4. © Sun Technologies Inc.
Running and checking whether Ant is installed in the system .
4

5. © Sun Technologies Inc. 5
Writing build.xml file in Notepad

6. © Sun Technologies Inc. 6
Running build.xml file in command prompt

7. © Sun Technologies Inc. 7
Running hello.xml file

8. © Sun Technologies Inc.
Executing hello.xml in command prompt
8

9. © Sun Technologies Inc.
Executing hello.xml in command prompt
9

10. © Sun Technologies Inc.
Writing Second target in hello.xml
10

11. © Sun Technologies Inc.
Executing Second target of hello.xml in command prompt
11

12. © Sun Technologies Inc.
Executing build.xml in eclipse
12

13. © Sun Technologies Inc.
Executing build.xml in eclipse
13

14. © Sun Technologies Inc.
Executing run target
14

15. © Sun Technologies Inc.
Executing run target in eclipse
15

16. © Sun Technologies Inc.
Executing second run target in eclipse
16

17. © Sun Technologies Inc.
Sample Ant build.xml
17

18. © Sun Technologies Inc.
Apache Maven
18
Apache Maven is a open source build testing tool. It will check the
compilation issue in entire framework based on the concept of a
project object model (POM), Maven can manage project's build,
reporting and documentation.

19. © Sun Technologies Inc.
Apache Maven features
19
 Maven has conventions.
It knows where your source code is because you followed the convention. Maven’s
Compiler plugin put the bytecode in target/classes, and it produces a JAR file in
target.
 Maven is declarative.
All you need to do is create a pom.xml file and put your source in the default
directory. Maven will take care of the rest.

20. © Sun Technologies Inc.
Apache Maven Installation
20
 Download latest version of maven and unzip the folder.
 Copy the bin path.
 Go to environment variables find path variable and edit and paste the bin path.
 Create a new variable as Maven_Home and paste the path of Maven.
 And the Java_Home should contain path of the java.
 Go to command prompt and check whether maven is installed or not by typing
mvn –version.

21. © Sun Technologies Inc.
Apache Maven Installation
21

22. © Sun Technologies Inc.
Downloading jars from command prompt
22

23. © Sun Technologies Inc.
Apache Maven Installation
23
First we need to add all the dependencies to pom.xml file.
Then run,
 mvn compile is a command to get dependencies jar from internet
It will download Jars from internet based on pom.xml file.
 mvn install
Command for executing test script from command prompt.

24. © Sun Technologies Inc.
Apache Maven with eclipse
24
 Install maven plugin in eclipse
Help -> install new software
install the plugin m2e - Maven Integration for Eclipse
 Install java

25. © Sun Technologies Inc.
Apache Maven with eclipse
25

26. © Sun Technologies Inc.
Apache Maven with eclipse
26

27. © Sun Technologies Inc.
Apache Maven with eclipse
27

28. © Sun Technologies Inc.
Apache Maven with eclipse
28

29. © Sun Technologies Inc.
Apache Ant VS Maven
29
ANT,
doesn't have formal conventions like a common project directory structure,
you have to tell Ant exactly where to find the source and where to put the
output.
is procedural, you have to tell Ant exactly what to do and when to do it. You
had to tell it to compile, then copy, then compress.
doesn't have a lifecycle, you had to define goals and goal dependencies. You
had to attach a sequence of tasks to each goal/target manually.

30. © Sun Technologies Inc.
Apache Ant VS Maven
30
Maven,
 has conventions, it already knew where your source code was because you followed
the convention. It put the bytecode in target/classes, and it produced a JAR file in
target.
 is declarative. All you need to do is create a pom.xml file and put your source in the
default directory. Maven will take care of the rest.

31. © Sun Technologies Inc. 31
Thank you