Message-ID: <1610555508.99.1429491662842.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_98_493906988.1429491662842" ------=_Part_98_493906988.1429491662842 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
All information in this wiki is licensed under the = Apache License, version 2.0. Please keep this in mind when you contribu= te.
This wiki space is not for final documentation, but a workspace for crea= ting it. If you think a document can be contributed back to the main site, = please record that in JIRA. For discussions, ideas and design documents rel= ated to Maven, see the Maven space.= p>
If you're a Java software developer that has worked in any type of team = environment, you know that having a proper process is important to developi= ng a quality product. You also know that rote methods can help maintain con= sistency and standardization among developers. Apache ANT provides most of = this however Maven improves upon it in several areas. Maven takes some of t= hat classpath and jar dependency frustrations out of the hands of the day-t= o-day developer. Most would agree that maintaining the project structure, d= ependencies, J2EE packaging, etc. is very difficult and when things are not= structured correctly, applications cannot be built properly. Jars could be= in the wrong place, be the wrong version, an XML file might be missing a d= escriptor, and a host of other project infrastructure issues can bring a pr= oject to stop. When this happens its sometimes difficult to determine where= things went wrong. Maven is an excellent tool that solves most of th= ese problems.
While the typical project manager might disagree, Maven meets the projec= t manager and the development staff somewhere in the middle. Apache's ANT i= s a powerful tool, but there's no standardization in targets. In fact, it m= ay be too customizable. Maven did right by holding to a distinct set of bui= ld lifecycle goals. If you're the do-it-yourself type, you can create your = own plugins to extend the functionality of Maven. Project managers want con= trol and Maven injects this technical control into the build process. Maven= assures everyone that the build and deploy process is done the same every = time. Musicians practice scale repetition for this very reason. Rote proces= ses are very effective because their consistency and effectiveness save tim= e and assure quality.
The documentation listed in the table of contents is meant to be a place= to begin to learn how to use Maven. Many development shops and software gr= oups may be using Maven1 now. If you are, please take a look at Maven2. For= anything to become a standard, it must be proven to be the standard by our= use. Let's make Maven(2) the standard in our build process. Let's go write= quality software and let Maven do our heavy lifting.
Here are some ways you can contribute:
Looking for some documentations you can't seem to find? - Request for a = wiki documentation by adding a list = here.
Want to write a wiki documentation but don't know where to put it? - Wri= te it first here, then let's tra= nsfer it later.
Material on Maven 2, outside the maven site.