maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mirko Friedenhagen <mfriedenha...@gmail.com>
Subject How Maven works - definitions
Date Sun, 07 Jul 2013 09:56:23 GMT
Hello,

I did not find an overview and now am trying to explain firstly myself
and afterwards maybe others how Maven works (to other developers):

- Maven is a declarative tool to build software, which relies mainly
on conventions.
- Declarations are done in a XML file called pom (project object model).
- Maven consists of a small core and a plethora of plugins.
- Maven builds stuff (often binaries) following paths outlined in
lifecycles, predefined lifecycles are called "default", "clean" and
"site".
- Lifecycles are sequences of phases like e.g. compile, test or install.
- Plugins provide a multitude of so called goals, which do specific
stuff like e.g. compiling java source to classes or running unit
tests.
- The execution of goals is often bound to lifecycle phases.
- There are standard definitions which goals should be run during a
phase of a lifecycle and this is mostly dependent on the packaging,
the type of binary produced. It makes no big sense to run the
compiling goal for java sources on a project which only holds a pom,
which is a XML file.

Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message