Maven nutshell
Upcoming SlideShare
Loading in...5
×
 

Maven nutshell

on

  • 596 views

Bas

Bas

Statistics

Views

Total Views
596
Views on SlideShare
592
Embed Views
4

Actions

Likes
0
Downloads
15
Comments
0

2 Embeds 4

http://www.linkedin.com 3
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Maven nutshell Maven nutshell Presentation Transcript

  • Maven Nutshell The Main Concepts Valerio Capozio 1 of 14
  • Apache Maven Maven is a build automation tool, developed and managed from Apache SoftwareFoundation. Maven serves a similar purpose of Apache Ant tool, but it offers an unparalleled softwarelifecycle management, providing a cohesive suite of verification, compilation, testing, packaging,reporting, and deployment plugins. Maven uses a convention over configuration approach to builds. Maven is typically used in Java projects, but it can be used also to manage projects in C#,Scala, Ruby and more other languages. Valerio Capozio 2 of 14
  • Project Object Model Maven revolves around a metadata file, namedpom.xml A file with this name has to exist in the root ofevery Maven project. In this file are defined the plugins to use, paths The snippet above shows the minimum information needed to define uniquely a Maven project through aand settings to override the Maven defaults of Pom.your project. A Maven project produces an element, such as JAR, WAR, EAR, etc uniquely identified by a vector of fields (groupId, Each POM inherits automatically from a Super artifactId, packaging, version).POM, a virtual POM embedded in the Maven core. A syntax to refer a specific Maven artifact is a string of vector elements, colon separated: Maven supports natively multi-module projects. groupId:artifactId:packaging:version http://maven.apache.org/guides/introduction/introduction-to-the-pom.html Valerio Capozio 3 of 14
  • Execution Hierarchy Maven splits execution into four nested hierarchies.From most-generic to most-specific they are: Lifecycle Phase Plugin Goal Lifecycle represents a well-recognized flow of steps. Phase is a step of lifecycle. Zero or more plugin goalsare bound to a phase. Plugin is a logical grouping and distribution of relatedgoals. Goal is a single executable task within a plugin. Valerio Capozio 4 of 14
  • Built-in Maven Lifecycle Maven has three built-in lifecycles: Clean Default Site Many of the phases within these three lifecycles are bound to a sensible plugin goal. Clean lifecycle deletes all generated artifacts from the output directory. Default lifecycle defines the commonly used phases to build an artifact, from its compilationto its installation on remote repository. Site lifecycle generates a project information web site and is able to deploy the artifacts to aspecified web server or local path. http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Valerio Capozio 5 of 14
  • Phases of Clean and Site Lifecycles Clean Lifecycle Site Lifecycle Phase Purpose Phase Purposepre-clean - pre-site Cross check that all elements necessary forclean Remove all generated and the build are correct and compiled artifacts in present. preperation for a fresh build. site Generate an HTML web site containing projectpost-clean - information and reports. post-site - site-deploy Upload the generated website to a web server. Valerio Capozio 6 of 14
  • Phases of Default Lifecycle 1/2 Default Lifecycle Phase Purposevalidate validate the project is correct and all necessary information is available.initialize initialize build state, e.g. set properties or create directories.generate-sources generate any source code for inclusion in compilation.process-sources process the source code, for example to filter any values.generate-resources generate resources for inclusion in the package.process-resources copy and process the resources into the destination directory, ready for packaging.compile compile the source code of the project.process-classes post-process the generated files from compilation (e.g. to do bytecode enhancement on classes)generate-test-sources generate any test source code for inclusion in compilation.process-test-sources process the test source code, for example to filter any values.generate-test-resources create resources for testing.process-test-resources copy and process the resources into the test destination directory.test-compile compile the test source code into the test destination directoryprocess-test-classes post-process the generated files from test compilation (e.g. to do bytecode enhancement on classes) Valerio Capozio 7 of 14
  • Phases of Default Lifecycle 2/2 Default Lifecycle Phase Purposetest run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed.prepare-package perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package. (Maven 2.1 and above)package take the compiled code and package it in its distributable format, such as a JAR.pre-integration-test perform actions required before integration tests are executed. This may involve things such as setting up the required environment.integration-test process and deploy the package if necessary into an environment where integration tests can be run.post-integration-test perform actions required after integration tests have been executed. This may including cleaning up the environment.verify run any checks to verify the package is valid and meets quality criteria.install install the package into the local repository, for use as a dependency in other projects locally.deploy done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects. Valerio Capozio 8 of 14
  • Dependency To express the reliance of our project on a particular artifact is possible declare a dependency in the Pom file. Each dependency can specify a scope, which manages its visibility and inclusionScope Description in the final artifact.compile Needed for compilation, included in packages. Maven manages automatically thetest Needed for unit tests, not included in packages. transitive dependencies.provided Needed for compilation, but provided ar runtime. Dependency scope can affect thesystem Needed for compilation, given as absolute path on disk and not included in packages. transitivity mechanism.import Inline inclusion of a POM-type artifact. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Valerio Capozio 9 of 14
  • Plugins A plugin and its configuration are added with a declaration, very similar to a dependency, in the build section of the Pom file. Mojo is the acronym of the Maven plugin classes and derives from Common Plugins aggregation of “Plain Old Java Object” andsurefire Runs unit tests “Maven Java Object”.checkstile Check the code’s stylingassembly Create ZIP and other distribution packages. Valerio Capozio 10 of 14
  • Repository Repositories are used to hold collections of Maven artifacts and dependencies. Exist only two type of repositories: local and remote. Local repository refers to a copy on your own installation. This repository is a cache Popular Repositories copy of the remote downloads.Maven http://repo1.maven.org/maven2/ Remote repositories are any other typeCodehaus http://repository.codehaus.org/ of repository accessed by some protocolJBoss http://repository.jboss.org/maven2 (e.g. http:// file:// etc.) Valerio Capozio 11 of 14
  • Profiles With profiles can specify particularbehaviors on portions of Mavenconfiguration, including plugins, pathing andconfiguration. They modify the POM at build time, andare meant to be used in complementary setsto give equivalent-but-different parameters The snippet above shows an example of profilefor a set of target environments. declaration. A profile can be triggered/activated in several ways: A typical use of profiles is for build-time Explicitly Through Maven settingscustomization of JAR dependencies based on Based on environment variables OS settingsthe use of a specific Application Server. Present or missing files http://maven.apache.org/guides/introduction/introduction-to-profiles.html Valerio Capozio 12 of 14
  • About me Valerio Capozio Website angelusworld.com Linkedin linkendin.com Slideshare slideshare.net Twitter twitter.com Valerio Capozio 13 of 14
  • ThanksValerio Capozio 14 of 14