1. Venkaiah Chowdary Koneru
Fazreil Amreen Abdul Jalil

2. Agenda
• Maven
• Repository
• Complete Build solution

3. What’s the Problem?
• Manual handling of external Jars
• Inter-project dependencies
• Running tests

4. What is Maven ?
• A build tool
• Uniform build system
• Provides quality project information
• Transparent migration to new features
• Guidelines for best practices development

5. Conceptual Model
• Maven maintains model of a project
• Unique set of coordinates to a project
• Almost zero effort
• Encourages modular design

6. Default Directory Structure
Structure is based on the archetypes
definition
Source folders
Test related
Source folders
Generated class files
and artifacts

7. POM
• Fundamental unit of work in maven
• An XML file
• Consists
– Project information
– Project relationships
– Build settings
– Build environment

8. POM <project ...>
<parent />
<groupId />
• Fundamental unit of work in maven
<artifactId />
<version />
<packaging />
<modules> … </modules>
• An XML file <propertie> ... </properties>
<developers />
<contributors />
<scm> ... </scm>
• Consists <build>
<plugins> ... </plugins>
– Project information
</build>
<dependencies> ... </dependencies>
– Project relationships </repositories>
<repositories> ...
<pluginRepositories> ... </pluginRepositories>
– Build settings ... </profiles>
<profiles>
<reporting> ... </reporting>
– Build environment
</project>

9. POM
• Convention over Configuration
• Maven incorporates this by providing
default behavior for projects
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>my.fazreil.projects</groupId>
<artifactId>fireglass</artifactId>
<version>0.0.1</version>
</project>
Just put your sources in the
correct directory

10. Life Cycle
• Contains phases in specific order
• Phase is made up of goals
• 3 built-in life cycles
– default
– clean and
– test

11. Life Cycle - Default
validate
initialize
test-
compile test package
compile
deploy install

12. Multi-Module Projects
• Why use a modular architecture ?
– Separation of concerns
– Easier to test
– Flexible
• Reusing the configuration
– Inheritance
– Dependencies
• Aggregation

13. Multi-Module Projects
Organization or team wide
properties
archetype
Project wide properties
Project
Aggregation
module1 module2
Module specific properties

14. Multi-Module Projects
• Organize your builds
• Speed up builds
• Speedup test process

15. Maven Repository
• Holds the build artifacts and dependencies
• Two types of repositories
– Local
– Remote

16. Local Repository
• Local cache for artifacts
• Can erase it completely
• Useful for offline builds
• Resides in User home’s .m2/ folder

17. Remote Repository
• Central repository to host all artifacts
• Local repository downloads from the
central repository hosted @ maven.org
Local Repository
Search order
(.m2repository)
Remote repository
(http://repo1.maven.org/maven2)

18. Internal Repository
• Corporate repository
• Proxy for remote repositories
Local Repository
(.m2repository)
Search order
Internal Proxy
(http://{repository url})
Remote repository
(http://repo1.maven.org/maven2)

19. What is Artifactory?
• It is a MAVEN repository
• Think of it as the ‘SVN’ for libraries.
• It is the place to obtain this information:
<dependency>
<groupId>my.fazreil.project</groupId>
<artifactId>fireglass</artifactId>
<version>0.0.1</version>
</dependency>

20. Do we need our own maven
repo?
• Because we want to host our own
libraries.
• And we would like to make our libraries
available to the local network
• Yes, we can control the access.

21. Extra notes
• Artifactory acts as a proxy to the outside
repository.
• Dependencies requested to Artifactory will
be cached in Artifactory for quick retrieval.

22. Build solution
• Complete end-to-end solution
• 5 open source projects
– Maven
– Subversion
– Hudson
– Artifactory
– Sonar

23. Ecosystem
• A typical maven project ecosystem
Distribute artifacts
Publish
artifacts
Source code Automated
builds metrics
changes

24. Maven Release Cycle
• Develop against snapshot versions
• Release stable versions
• Automated releases
– Update version numbers to next SNAPSHOT
versions