adding henning

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@293431 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2005-10-03 18:51:14 +00:00
parent 63b3f71f6d
commit 1f3ad56547
1 changed files with 13 additions and 1 deletions

View File

@ -88,6 +88,18 @@ with the dependency management mechanism you have to try to screw up your jar ve
there is a strong defined lifecycle that a software system goes thru from the initiation of a build to the end...and the users are allowed to mix and match their system to the lifecycle instead of cobble together their own lifecycle.. this has the additional benefit of allowing people to move from one project to another and speak using the same vocabulary in terms of software building
henning
1) (most important) quick project setup, no complicated build.xml
files, just a POM and go
2) all developers in a project use the same jar dependencies due to
centralized POM.
3) getting a number of reports and metrics for a project "for free"
4) reduce the size of source distributions, because jars can be pulled
from a central location
+-----+
+-----+