Hi Ricardo, Lachlan gave you a great overview of why use Maven. If you want to know more, look at [1]. I've added some links about general Maven stuff.
Just to summarize, Maven handles the entire lifecycle of a project - from project creation, to build, deploy and versioning (SCM and binary). It can also generate a site with documentation and reports about the healthy of your project. [1]http://wiki.objectstyle.org/confluence/display/WOL/General+Maven+Documentation Cheers, Henrique On Wed, Jun 11, 2008 at 4:19 AM, Lachlan Deck <[EMAIL PROTECTED]> wrote: > Just some random thoughts... > > On 11/06/2008, at 4:16 PM, Ricardo Parada wrote: > >> I know very little about maven. Why would one want to build apps this way > > Lots of reasons. Some WO(Lips) particulars > - classpath works ;-) It's all defined once. > - not dependent on installed environment (e.g., spurious wobuild.properties, > custom ant stuff) > - don't need to switch installed environments > > More seriously, someone else may be able to summarise its benefits more > succinctly. The best thing to do as an into (I think) is to read up on maven > to see if you'd like to use it: > - http://maven.apache.org/ > - http://maven.apache.org/guides/getting-started/index.html > > The second one listed above will run you through the overall concepts and is > quite helpful in introducing you to the various aspects of maven. Pay > particular attention to the links from that page (e.g., to the maven model - > which describes the various xml elements and what they do). > > Installing maven is simple. e.g., (for mac) > # install macports if not present already (macports.org) > $ sudo port -d selfupdate > $ sudo port install maven2 > >> and use this project structure? > > The default project structure (as shown) is the recommended one. It's the > standard maven layout. The reasons for this is so that, from project to > project, any developer knows where to find things, where to put things - > whether familiar with WO or otherwise and also Maven's build system does > stuff by default (without need for further configuration) with these > files/resources when compiling/packaging/installing/testing etc. > > The mantra is standard conventions over configuration. [1] > > You can configure things (which I've done for transitioning) to work with > your current bunny layout. e.g., if you're just wanting to kick the tyres so > to speak. I'll write up how to do this on the wiki over the next day or so. > It's pretty simple. > > It's helpful to read [2] first to get the idea of things, but [3] shows you > how to configure things for your build. > >> Is it so that it builds your projects and apps with the right version of >> WO and other jars? > > It will build it with what you define, sure. > >> The deployed app will then use / include the version specified during the >> build? Is that what this is for? > > It will do that too. But this is not specifically what it's for as you can > do that already with ant or any other build system. > > [1] http://maven.apache.org/benefits-of-using-maven.html > [2] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > [3] http://maven.apache.org/ref/2.0.8/maven-model/maven.html > > with regards, > -- > > Lachlan Deck > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com > > This email sent to [EMAIL PROTECTED] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
