Hi,
well it really depends on to whom you want to sell it.
Some ideas:
- easy to generate IDE project files (or use native IDE import/sync with
IDEA 7): estimate the time to setup the environment for a new developer
in the current setup vs. mvn eclipse:eclipse
- don't reinvent the wheel: count the hours you spend maintaining your
ant scripts and tasks vs just using the plugins provided by Maven
- governance: provide a company wide repo with the jars that are
approved to be used
- site: greatly improves inner and inter project communication, helps to
leverage reuse across projects
We've sold it together with subversion ("the successor of cvs") as the
successor of ant.
An additional advantage was to greatly reduce build time: while
previously everything had to be built from scratch, the build process is
much more modular now. Building one module now uses prebuild (SNAPSHOT)
jars of the dependant modules instead of compiling them. Of course that
could also be achieved with ant, but it was easy to attribute that to
Maven :-)
=Stefan
--
reuter network consulting
Neusser Str. 110
50760 Koeln
Germany
Telefon: +49 221 1305699-0
Telefax: +49 221 1305699-90
E-Mail: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED]
Steuernummern 215/5140/1791 USt-IdNr. DE220701760
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
