http://developer-blog.cloudbees.com/2013/04/the-maven-way.html
On 16 April 2013 16:16, Stephen Connolly <[email protected]>wrote: > > > > On 16 April 2013 16:11, Mark H. Wood <[email protected]> wrote: > >> On Mon, Apr 15, 2013 at 09:48:35PM +0100, Stephen Connolly wrote: >> [snip] >> > The reality is that the true goal of the Maven Way™ is that your pom >> should >> > be as close as possible to the following >> > >> > <project> >> > <groupId>...</groupId> >> > <artifactId>...</artifactId> >> > <version>...</version> >> > <packaging>...</packaging> >> > <dependencies> >> > ... >> > </dependencies> >> > </project> >> > >> > Every line you add to the above is moving further from the Maven Way™ >> >> Brilliant. The above describes what the project *is*. The more you >> have to tinker with plugins and the like, the more likely you are >> describing *how the project should be built*. But if I have >> understood the situation, Maven exists to figure out *how* after you >> have told it *what*. >> > > Yep, exactly! > > >> >> -- >> Mark H. Wood, Lead System Programmer [email protected] >> Machines should not be friendly. Machines should be obedient. >> > >
