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 hidden :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/
On Sat, Jul 13, 2013 at 5:30 PM, Martin Gainty <mgai...@hotmail.com> wrote: > If you want to discover how a house was built you need to talk to an Architect > > The Architecture of maven is a loose Framework which constitute One of 3 > default Maven lifecycles > http://maven.apache.org/ref/3.0.5/maven-core/lifecycles.html > > Each Maven lifecycle in turn consists of one or more phases which will allow > multiple Modello architected plugins (spec v 4.0.0 of Modello) to be bound to > that phase in order to execute the plugins goal for their Mojo class > http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/utilizing-the-build-life-cycle/ > > In order for use to provide further clarification we would need to know > which tasks you wish to run > > HTH > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger > sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung > oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich > dem Austausch von Informationen und entfaltet keine rechtliche > Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen > wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire informez > l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci > est interdite. Ce message 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, 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 <mfriedenha...@gmail.com> 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 until you encounter problems or wish to >> > extend stuff. I deal a lot with supporting our department (roughly 200 >> > developers, 150 of whom are using Maven) and I am always reiterating >> > explaining the basic glossary (phase, lifecycle, goal). >> > >> > While the "Complete reference" by Sonatype is great once you know the >> > basics, it is quite extensive and not every application developer >> > wants or needs to delve throught it :-) >> >> I will agree the documentation could be improved. >> >> I've also said in the past that one of Maven's problems is that it >> just works for most people. >> >> Compare that to Ant where before you can build a project you must read >> the README, configure your project settings file and then try to >> build, often trouble shooting by looking at the Ant website. This >> means the average user of Ant has picked up more stuff because they >> are forced to. >> >> In Maven only the person who is modifying the poms generally acquires >> more in depth knowledge of Maven - including terminology. >> >> Which means when someone does need to work out what went wrong there >> is a steep learning curve because it was not amortized over time. >> >> Ideas on how to fix that are welcome. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
