Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: copyedits


This wiki space is not for final documentation, but a workspace for creating 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 related to Maven, see the Maven space.


If you're a java Java software developer that 's has worked in any type of team situationenvironment, you know that the a proper process is important to developing a quality product. Also, you know, that rote methods maintain consistency and standardization among developers. Apache ANT does that for some of us very well . Maven kicked it up a notch however Maven improves upon this in several areas. Maven took some of that classpath and jar dependency frustration out of the hands of the day-to-day developer. Most will would agree with me that maintaining the project structure, dependencies, J2EE packaging, etc. is very difficult . When and when things are not structured correctly, applications don't work. Jars could be in the wrong place, jars could be the wrong version, an XML file might be missing a descriptor, and a host of other project infrastructure issues can bring a project to stop. When this happens it's sometimes difficult to determine where things are went wrong. And, most developers aren't up on all their J2EE archive types. Nor do they focus on the trivia of J2EE descriptors. Developers Maven is an excellent tool that solves most of these problems.

While the stereotypical typical project manager might disagree with me, Maven meets the project manager and the development staff somewhere in the middle. Apache's ANT is a powerful tool, but there's no standardization in targets. In fact, it may be too customizable. Maven did right by holding to a distinct set of build 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 control and Maven injects this technical control into the build process. Maven assures everyone that the build and deploy process is done the same everytime. Musician's Musicians practice scale repetition for this very reason. Rote processes that work are very effective because their commonality and effectiveness save time and assure quality.