Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<h1>Trail : Maven 2 fundamentals - The Big Picture</h1>

<p>This trail explains the fundamentals of using Maven 2 to manage your projects. It focuses on the different Maven concepts users should fully understand before starting to learn how to use Maven to manage their project.</p>
<ul>
	<li><a class="confluence-link" href="/display/MAVENUSER/Maven%2C+not+just+another+build+tool" data-linked-resource-id="47833" data-linked-resource-type="page" data-linked-resource-default-alias="Maven, not just another build tool" data-base-url="http://docs.codehaus.org">Maven, not just another build tool</a> : Find out how Maven distinguish itself and what sets it apart from the other build tools.</li>
</ul>

<ul>
	<li><a class="confluence-link" href="/pages/viewpage.action?pageId=47832" data-linked-resource-id="47832" data-linked-resource-type="page" data-linked-resource-default-alias="The Project Object Model (POM)" data-base-url="http://docs.codehaus.org">The Project Object Model (POM)</a>: The POM is the heart and soul of any Maven enabled-project. It contains every bit of information Maven needs to know about your project.</li>
	<li><a class="confluence-link" href="/display/MAVENUSER/Naming+Conventions" data-linked-resource-id="47929" data-linked-resource-type="page" data-linked-resource-default-alias="Naming Conventions" data-base-url="http://docs.codehaus.org">Naming Conventions</a>: Maven needs to be able to identify every project artifact precisely. Each deployed artifact has to respect Maven naming conventions.</li>
</ul>

<ul>
	<li><a class="confluence-link" href="/display/MAVENUSER/The+Standard+Directory+Layout" data-linked-resource-id="48030" data-linked-resource-type="page" data-linked-resource-default-alias="The Standard Directory Layout" data-base-url="http://docs.codehaus.org">The Standard Directory Layout</a>: One of the most common things project should share is a standard directory layout. Maven recommends (but doesn't enforce) a standard project directory layout.</li>
</ul>

<ul>
	<li><a class="confluence-link" href="/display/MAVENUSER/The+Build+Lifecycle" data-linked-resource-id="48230" data-linked-resource-type="page" data-linked-resource-default-alias="The Build Lifecycle" data-base-url="http://docs.codehaus.org">The Build Lifecycle</a>: Maven is based around the central concept of a build lifecycle. What this means is that the process for building and distributing a particular artifact is clearly defined.</li>
	<li><a class="confluence-link" href="/display/MAVENUSER/Repositories" data-linked-resource-id="48524" data-linked-resource-type="page" data-linked-resource-default-alias="Repositories" data-base-url="http://docs.codehaus.org">Repositories</a>: A repository in Maven is used to hold build artifacts and dependencies of varying types. Repositories allow Maven to manage your project dependencies and automatically share components between different projects.</li>
</ul>

<ul>
	<li><a class="confluence-link" href="/display/MAVENUSER/Dependency+Management" data-linked-resource-id="48525" data-linked-resource-type="page" data-linked-resource-default-alias="Dependency Management" data-base-url="http://docs.codehaus.org">Dependency Management</a>: Dependency management is one of the features of Maven that is best known to users and is one of the areas where Maven excels. There is not much difficulty in managing dependencies for a single a project, but when you start getting into dealing with multi-module projects and applications that consist of tens or hundreds of modules this is where Maven can help you a great deal in maintaining a high degree of control and stability.</li>
</ul>