maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lennart Jörelid <lennart.jore...@gmail.com>
Subject Re: How Maven works - definitions
Date Sun, 07 Jul 2013 10:51:11 GMT
Hello there Mirko,

I'd suggest fine-tuning the lifecycle->phase->plugin description slightly:

   - Maven is a tool to build software, which relies mainly on conventions.
   - The build is configured in an XML file called pom (project object
   model, or "pom file").
   - Maven consists of a core and a plethora of plugins. Plugins can be
   included in the build by being configured within the pom file.
   - Maven builds stuff (often binaries) according to recipes outlined
in lifecycles.
   Predefined lifecycles are called "default", "clean" and "site".
   - Lifecycles consist of sequences of named steps, called phases. The
   names of all phases are standarized, such as "compile", "test" or "install".
   - When Maven executes a phase, it announces the phase name to all
   plugins included in the build.
   - Plugins contain methods which perform specific actions like e.g.
   compiling java source to classes or running unit tests. These methods
   are given a symbolic name, called "goal", and configured to run within a
   specified phase (known as "binding" a goal to a phase).
   - 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 contains images but no source code, for
   example.





2013/7/7 Mirko Friedenhagen <mfriedenhagen@gmail.com>

> 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
>
>


-- 

--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message