intro into build systems and build automation for iasi-jug.ro

1. Java Builds at a Glance
By Gabriel Dogaru

2. Agenda
● Apache Ant
● Apache Maven
● Gradle
● Quickstart

3. Wich build tool do you use?
● Make
● Ant
● Maven
● Gradle
● Rake
● Simple Build tool
● Buildr
● Eclipse
● Intellij
● Netbeans
● Gant
● SuperMake
● Hyper Build
● Other ???

5. Why use a build tool
● Your friend might want the code
● You may get old and forget stuff
● An IDE will change
● You are a professional

6. Your build Tool
● Imperative
● Declarative

7. Apache Ant
● Apache Ant is a Java library and
command-line tool whose mission is to
drive processes described in build files
as targets and extension points
dependent upon each other.

8. Apache Ant
● ANT stands for “Another Neat Tool”
● ANT evolved from the UNIX based build
utility called “MAKE”.
● Ant has Java Class like extensions
● Use of XML instead of Shell Scripts
● Each task is taken care by creating its object
● Standardized
● Platform Independent

9. Apache Maven
● Maven, a Yiddish word meaning
accumulator of knowledge, was originally
started as an attempt to simplify the build
processes in the Jakarta Turbine project.

10. Apache Maven Goals
● Making the build process easy
● Providing a uniform build system
● Providing quality project information
● Providing guidelines for best practices
development
● Allowing transparent migration to new
features
● Convention over onfiguration

11. Gradle
● Gradle is build automation evolved.

12. Gradle
● Gradle combines the power and flexibility
of Ant with the dependency management
and conventions of Maven into a more
effective way to build.
● Powered by a Groovy DSL

13. Let's make a project

14. Round up
● Ant is old but popular
● Maven is cool
● Gradle is cool, could get cooler
● Use the best tool for the job

15. Thank You!