Saturday, April 10, 2010

MAVEN getting started, Maven in 10 Minutes

Download and unzip into any where (In my case it is D:\Software\apache-maven-3.0-alpha-7)
set path D:\Software\apache-maven-3.0-alpha-7\bin

open dos console and type mvn -v
To check for sucessfully install.

Create one folder to practice for maven project say D:\binod\Maven_Practice
Now execute command from dos console
D:\binod\Maven_Practice>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.tecnotree.bds -DartifactId=CheckMaven

CheckMaven is the project name
command exectued from D:\binod\Maven_Practice
it create one folder CheckMaven inside D:\binod\Maven_PracticeInside CheckMaven : src folder and pom.xml file
<project xmlns="" xmlns:xsi="" xsi:schemaLocation=""&gt; <modelVersion>4.0.0</modelVersion> <groupId>com.tecnotree.bds</groupId> <artifactId>CheckMaven</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>CheckMaven</name> <url></url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies></project>
src -> main and test. main -> java -> com -> tecnotree -> bds -> App.javatest -> java -> com -> tecnotree -> bds ->

package com.tecnotree.bds;
public class App {
public static void main( String[] args ) {
System.out.println( "Hello World!" );

package com.tecnotree.bds;
import junit.framework.Test;
import junit.framework.TestCase;
import junit.framework.TestSuite;

/** * Unit test for simple App. */

public class AppTest extends TestCase{
/** * Create the test case * * @param testName name of the test case */
public AppTest( String testName ) { super( testName ); }
/** * @return the suite of tests being tested */
public static Test suite() { return new TestSuite( AppTest.class ); }
/** * Rigourous Test :-) */
public void testApp() { assertTrue( true ); }

D:\Binod\Maven_Practice\CheckMaven> mvn compile
It compile and create new folder target and App.class put into D:\Binod\Maven_Practice\CheckMaven\target\classes\com\tecnotree\bds

without running above commannd
D:\Binod\Maven_Practice\CheckMaven>mvn test-compile then it will compile and and put App.class into D:\Binod\Maven_Practice\CheckMaven\target\classes\com\tecnotree\bdsand into D:\Binod\Maven_Practice\CheckMaven\target\test-classes\com\tecnotree\bds

without running any above command
D:\Binod\Maven_Practice\CheckMaven> mvn test
It will do mvn test-compile and extra test. Means in target there would be create three folderlike about classes and test-classes and new is surefire-report.

Actually mvn test it runs the compiled unit tests and make report (txt & xml) and put into surefire-report folder.
This command will also show test result on console.

D:\Binod\Maven_Practice\CheckMaven> mvn package
It would be work of mvn test and extra create one folder maven-archiver and put one jar file CheckMaven-1.0-SNAPSHOT.jar into target folder.
Inside the maven-archiver one file would be come with these details:
#Generated by Maven#Sat Apr 10 10:34:57 EEST 2010version=1.0-SNAPSHOTgroupId=com.tecnotree.bdsartifactId=CheckMaven

D:\Binod\Maven_Practice\CheckMaven>mvn integration-test
It will execute all above command internally and carries out acutal integartion tests. Right now no any differences from above command. We will see later.

Without running any above command
D:\Binod\Maven_Practice\CheckMaven> mvn install
It will run above command interally and adds the archive to the local Maven directory. This makes it available for any other modules that may depend on it.

My local repository set up into D:\.m2 folder.
(How to set up custome local maven repository:
I have install or unzip Maven file here D:\Software\apache-maven-3.0-alpha-7. Go into D:\Software\apache-maven-3.0-alpha-7\conf and change settings.xml
uncommented <localRepository> and changed to <localRepository>D:\.m2\repository</localRepository>
so, CheckMaven-1.0-SNAPSHOT.jar put into D:\.m2\repository\com\tecnotree\bds\CheckMaven\1.0-SNAPSHOT

Without running any above command
D:\Binod\Maven_Practice\CheckMaven> mvn deploy
It will run above command interally and adds the archive to the remote Maven directory. But here it wont work.
Because we dont have set up the repository element was not specified in the pom inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]

How to set remote maven repository.

open pom.xml (D:\Binod\Maven_Practice\CheckMaven\pom.xml)
Add <distributionManagement> like this
<project xmlns="" xmlns:xsi="" xsi:schemaLocation=""&gt; <modelVersion>4.0.0</modelVersion> <groupId>com.tecnotree.bds</groupId> <artifactId>CheckMaven</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>CheckMaven</name> <url></url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> <distributionManagement> <repository> <id>BinodprojectRepository</id> <name>Binod Maven Repository Name</name> <url>file:///d:/MyRemoteMavenRepository</url>
</repository> <!-- site> <id></id> <url>dav:</url> </site --> </distributionManagement>

Now you will see after run mvn deploy.
one target file will be created as usual and archieve file will go to d:/MyRemoteMavenRepository (no need to createthis folder, it create automatically).
D:\Binod\Maven_Practice\CheckMaven> mvn cleanIt will delete the target forlder.

************************ CONCLUSION ********************
There are phases of the default life cycle of Maven
1. validate : Ensures that the current configuration and the content of the POM is valid. This includes validation of the tress of pom.xml files.
2. compile : Compiles the source code. The compiled classes are places into a target directory tree.
3. test-compile : Compile the source code of the unit tests.
4. test: Runs the compiled unit tests and showing the result on the console.
5. package: Bundles the exectable binaries into a distribution archive, such as a JAR or WAR.
6. integration-test : Carries out actual integration tests.
7. install : Adds the archive to the local Maven directory. This markes it available for any other modules that may depends on it.
8. deploy : Adds the archive to a remote Maven directory. This can make the artifact available to a larger audience.

Concept is here that if you run 3 then it will run 1, 2 and 3.
if you run 6 then it will run 1,2,3,4,5 and 6.
That is because if you call a build phase, it will execute not only that build phase, but also every build phase prior to the called build phase.

It should also be noted that the same command can be used in a multi-module scenario (i.e. a project with one or more subprojects). For example:mvn clean install (from root directory), this command will traverse into all of the subprojects and run clean, then install (including all of the prior steps).

mvn install -Dmaven.test.skip=true : it will do install but except test execution.

How to integrate with Eclipse
Now if you want to import this project into eclipse, it will not work. In eclipse you would not be able to import this project.
D:\Binod\Maven_Practice\CheckMaven> mvn eclipse:eclipse
It will create two file inside D:\Binod\Maven_Practice\CheckMaven folder. 1. .classpath and 2. .project. Now you can import into eclispe.

Open eclipse and set workplace is D:\Binod\Maven_Practice. File -> Import -> Import -> General -> Existing Projects into Workspace -> Browse (Select root directory, D:\Binod\Maven_Practice)then check CheckMaven -> Finish

Your project would be imported into workspace.
D:\Binod\Maven_Practice\CheckMaven> mvn eclipse:cleanIt will delete both generated file 1. .classpath and 2. .project.

D:\Binod\Maven_Practice\CheckMaven>mvn eclipse:clean eclipse:eclipse
Now we ensured that all previous eclipse resources are removed and generated again.
To let eclipse know where the local Maven 2 repository is located you should know where it is located. By default the Maven 2 repository is located at
/home/[USERNAME]/.m2/repositoryC:\Documents and Settings\sumankbi\.m2\repository
We should avoid avoid space in maven repository class path. Refer above settign to change local repository.

In Eclipse -> window -> Preferences -> Maven -> Installation -> User setting -> Browse -> D:\Software\apache-maven-3.0-alpha-7\conf\settings.xml then Local repository will be change as per the setting.xml and it become D:\.m2\repository.

Now check, In Eclipse -> window -> Preferences -> Java -> Build Path -> Classpath Variable -> M2_REPO shold be D:\.m2\repository.

mvn clean eclipse:clean eclipse:eclipse

Some dependencies often are needed to write your applications. Commonly we are using some open source libraries and frameworks (e.g. the spring application framework or apache commons-logging,...). Sometimes own libraries should be referenced by a java project. To solve this problem Maven delivers a very good dependency mechanism that manages the dependencies of your project transitivly.

How the maven download new jar file, if our project is needed for that jar file.
Maven will download all dependencies referenced by your pom.xml from the central Maven 2 repository automatically to local reposity (In my case D:\.m2\repository). Suppose my project is needed commons-logging jar file then put this jar info into pom.xml and run mvn package and watch console, maven will downloading this jar into your local repository.
You have to add commons-logging into pom.xml

<dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> </dependency>

Now complete pom.xml

<project xmlns="" xmlns:xsi="" xsi:schemaLocation=""&gt; <modelVersion>4.0.0</modelVersion> <groupId>com.tecnotree.bds</groupId> <artifactId>CheckMaven</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>CheckMaven</name> <url></url> <dependencies> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.5</version> <scope>test</scope> </dependency> </dependencies> <distributionManagement> <repository> <id>BinodprojectRepository</id> <name>Binod Maven Repository Name</name> <url>file:///d:/MyRemoteMavenRepository</url>
</repository> <!-- site> <id></id> <url>dav:</url> </site --> </distributionManagement>


Even I changed junit from 3.1 to 4.5. Now if I run mvn command (mvn clean package), it will download both jar file. You can watch d:\.m2\repository and console both.

Some more example

<groupId>org.springframework</groupId> <artifactId>spring-core</artifactId> <version>2.5.5</version> </dependency> <dependency>

<groupId>org.springframework</groupId> <artifactId>spring-webmvc</artifactId> <version>2.5.5</version>

<dependency> <groupId>org.springframework</groupId> <artifactId>spring-web</artifactId> <version>2.5.5</version> </dependency>

<dependency> <groupId>org.springframework</groupId> <artifactId>spring-jdbc</artifactId> <version>2.5.5</version> </dependency>

<dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>5.1.6</version> </dependency>

<dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> <version>1.1.2</version> </dependency>

Properties : Same as Ant, we can set up any variable and use in the xml file.
In above example we are repeating same version number of all the spring jar file, so better put one place all the version number and use references. Use the properties tag.


<!-- Spring Framework -->





Scopes: The dependency scope defines to which part of the project's lifecycle the dependency is attached. For example the JUnit dependency is only added while running the tests. So i defined that this dependency is attached to the target "test".


There are at least 6 different scopes:
compile: This scope indicates the Maven compilation phase. It is the default scope that will be used if no scope is defined. provided: This scope defines that this dependency is provided by the container (e.g. Apache Tomcat) at runtime. runtime: This scope indicates that this Dependency isn't required in the compilation phase but it is needed at runtime. test: "test"-dependencies are only while compiling and running the tests. system: This scope indicates that the dependency is provided by the system.

you must always think of a Maven POM in terms of the combinationof the Super POM, plus any parent POMs, and finally the current project’s POM. Maven starts with theSuper POM and then overrides default configuration with one or more parent POMs. Then it overridesthe resulting configuration with the current project’s POM.

Build element: it that handles things like declaring your project's directory structure and managing plugins; and the reporting element, that largely mirrors the build element for reporting purposes.

MultiProject in Maven

Create one folder say (MultiProjectCheck) D:\Binod\Maven_Practice\MultiProjectCheck
execute this command:
D:\Binod\Maven_Practice\MultiProjectCheck>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DartifactId=MultiProject

It will create MultiProject and put src and pom.xml.

Now go to pom.xml in D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject\pom.xmland change <packaging>jar</packaging> to <packaging>pom</packaging>.

By setting the packaging type to “pom”, any projects you generate from the root of the project directory will insert itself into the project by creating an entry into the modules section of the pom.xml for the site.

Now execute this below both command from MultiProject folder.

D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DartifactId=FirstSubModule

D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DartifactId=SecondModule

Now come to D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject\pom.xml (parent pom.xml), you will automatically added two module like this:

<module>FirstSubModule</module> <module>SecondModule</module>

You will see new tag in submodule pom.xml files.

<artifactId>MultiProject</artifactId> <groupId></groupId>

Now if you run mvn test from parent folder

then it will create target forlder in both module. But if you run mvn test from insidet FirstSubModule folder then it will be creating only in this module, it wont effect on second module SecondModule.

How to import into Eclispe:

D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject>mvn eclipse:eclipse

Create workspace in eclipse D:\Binod\Maven_Practice\MultiProjectCheck\MultiProjectand import -> browse -> select D:\Binod\Maven_Practice\MultiProjectCheck\MultiProject -> It will show both project, select both project and it will come to eclipse.

How to develop Maven site.
Maven site example.

come to D:\Binod\Maven_Practice
D:\Binod\Maven_Practice>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DartifactId=MavenSiteCheckand
execute this command to generate site folder inside src

D:\Binod\Maven_Practice>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site -DartifactId=MavenSiteCheck

go to D:\Binod\Maven_Practice\MavenSiteCheck\src\site\xdoc\xdoc.xml
Here you can write about your project.
D:\Binod\Maven_Practice\MavenSiteCheck>mvn site:site

It will create one target folder in D:\Binod\Maven_Practice\MavenSiteCheck.
One html file generate D:\Binod\Maven_Practice\MavenSiteCheck\target\site\xdoc.htmlyou can open this html file.

You can also run this page as web site using jetty
D:\Binod\Maven_Practice\MavenSiteCheck>mvn site:runURL: http://localhost:8080/xdoc.html

How you can put some picture here in documentcreate one resources inside the site folder (D:\Binod\Maven_Practice\MavenSiteCheck\src\site\resources) and put all your picutre here say suman.jpg

now come to xdoc.xml (D:\Binod\Maven_Practice\MavenSiteCheck\src\site\xdoc\xdoc.xml)
and write here <img src="suman.jpg"></img>
D:\Binod\Maven_Practice\MavenSiteCheck>mvn site:site

It will move all the images from D:\Binod\Maven_Practice\MavenSiteCheck\src\site\resources to D:\Binod\Maven_Practice\MavenSiteCheck\target\site.

now open D:\Binod\Maven_Practice\MavenSiteCheck\target\site\xdoc.html


  1. It's interesting that many of the bloggers to helped clarify a few things for me as well as giving.Most of ideas can be nice content.The people to give them a good shake to get your point and across the command.
    Java Training in Chennai

  2. Hello, I read your blog occasionally, and I own a similar one, and I was just wondering if you get a lot of spam remarks? If so how do you stop it, any plugin or anything you can advise? I get so much lately it’s driving me insane, so any assistance is very much appreciated.
    Data science Course Training in Chennai |Best Data Science Training Institute in Chennai
    AWS Course Training in Chennai |Best AWS Training Institute in Chennai
    Devops Course Training in Chennai |Best Devops Training Institute in Chennai
    Selenium Course Training in Chennai |Best Selenium Training Institute in Chennai