On 14 July 2013 04:52, Mirko Friedenhagen wrote:
> Martin,
>
> my point is mostly that while a lot of documentation is available, a
> short summary of the base concepts is hidden in all of this pages.
> Everything I wrote in my first email may be found in these pages, but
> I feel it is somewhat h
age sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>> Date: Mon
e: Mon, 8 Jul 2013 07:01:18 +0930
> Subject: Re: How Maven works - definitions
> From: baerr...@gmail.com
> To: dev@maven.apache.org
>
> On 8 July 2013 04:01, Mirko Friedenhagen wrote:
> > Hello,
> >
> > first of all, thanks for your replies. I think it would help v
On 8 July 2013 04:01, Mirko Friedenhagen wrote:
> Hello,
>
> first of all, thanks for your replies. I think it would help very much
> if an introductory would be at the plugin development page[1] to get
> the big picture. Or even be repeated at the the run[2] page.
>
> Running Maven is trivial unt
Hello,
first of all, thanks for your replies. I think it would help very much
if an introductory would be at the plugin development page[1] to get
the big picture. Or even be repeated at the the run[2] page.
Running Maven is trivial until you encounter problems or wish to
extend stuff. I deal a l
Well ... first of all, if documentation is considered important or
relevant, it should be easy to find.
The first principle of design is to make the function/use of an object
visible.
Currently, the main maven documentation for practically everyone (except,
perhaps, maven
developers who digs aroun
yes, such doc is useful IMHO, since it took myself a lot of time to get it
clear in my mind (particularly lifecycle->phase->goal)
for the moment, I didn't find energy to write it down since I didn't know where
to put it to get us work on improvements (and even if anybody would find it
useful)
Maybe worth understanding why the current online documentation did not
helped you. And maybe update it with this.
Thanks.
Sent from my iPhone
On 07 Jul 2013, at 12:51, "Lennart Jörelid" wrote:
> Hello there Mirko,
>
> I'd suggest fine-tuning the lifecycle->phase->plugin description slightly:
>
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
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 mo
10 matches
Mail list logo
