You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by jv...@apache.org on 2006/01/30 16:13:33 UTC
svn commit: r373524 -
/maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt
Author: jvanzyl
Date: Mon Jan 30 07:13:28 2006
New Revision: 373524
URL: http://svn.apache.org/viewcvs?rev=373524&view=rev
Log: (empty)
Modified:
maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt
Modified: maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt
URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt?rev=373524&r1=373523&r2=373524&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt (original)
+++ maven/site/trunk/src/site/apt/background/philosophy-of-maven.apt Mon Jan 30 07:13:28 2006
@@ -8,4 +8,29 @@
Philosophy of Maven
-~~I had a couple of slides on this in my javaZone presentation - trygve
+ Maven is generally considered by many to be a build tool. Many people who come to Maven initially are familiar
+ with Ant so it's a natural association but Maven is not just a build tool, and not just a replacement for Ant.
+ Maven is an entirely different creature from Ant. Ant is simply a toolbox whereas Maven is about the
+ application of patterns in order to acheive an infrastructure which displays the characteristics of
+ visibility, resuability, maintainability, and comprehensibility.
+
+ Without these characteristics it is highly improbable multiple individuals will work productively together
+ on a project. Without visibility it is unlikely an invidual will know what another has accomplished and as such
+ there is a very good chance useful code will not be resused. When code is not resused it is very hard to create
+ a maintainable system. When everyone is constanstly rooting around trying to figure out where all these different
+ bits and pieces are that make up your project there is very little chance anyone is going to comprehend the
+ project as a whole. As a result you end up with the silo effect, a decay of shared knowledge along with
+ the commensurate degree of frustration among team members. A natural effect when processes don't work
+ in the same way for everyone.
+
+ Maven was borne of the very practical desire to make several projects at Apache work in the same way. So that developers
+ could freely move between these projects, knowing clearly how they all worked by understanding how one of them
+ worked. If a developer spent time understanding how one project built it was intended that they would not have
+ to go through this process again when they moved on to the next project. The same idea extends to testing,
+ generating documentation, generating metrics and reports, testing and deploying. All projects share
+ enough of the same characteristics, an understanding of which Maven tries to harness in its general approach
+ to project management. On a very high level all projects need to be built, tested, packaged, documented
+ and deployed. Of course there is infinite variation in each of the above mentioned steps, but this variation
+ still occurs within the confines of a well defined path and it is this path that Maven attempts to present to
+ everyone in a clear way. The easiest way to make a path clear is to provide people with a set of patterns that
+ can be shared by anyone involved in a project.