The multiproject:install goal is quite useful, as it can't be done with a simple reactor call. It deals with the fact that the "install" goal's name changes depending on the type of artifact being built.
Similarly install-snapshot, deploy, deploy-snapshot, though I've not actually used them. Plain ol' multiproject:goal is less useful, I think. The only real advantage it offers over calling the reactor directly is that it provides reasonable defaults and so requires less typing. > -----Original Message----- > From: Andrew Bayer [mailto:[EMAIL PROTECTED] > Sent: 26 March 2004 17:19 > To: Maven Users List > Subject: RE: Quick reactor question > > > Hi, > Thanks, Peter - I already had **/project.xml in the > includes, so > it looks like I'm already set. > > That reminds me of something, though. I'm sure that > this is a > question with a fairly obvious answer, but I haven't been > able to quite > figure it out: what's the point of the multiproject plugin, > rather than the > reactor plugin? My build is going to be doing a lot of fairly > painful and > complex things, but I don't expect to use the site generation > functionality > in Maven at all. Given that, is there any reason for me to > use multiproject > rather than just the reactor? > > A. > > At 05:08 PM 3/26/2004 +0000, you wrote: > > >Ooops, hit send before I wanted to. ctrl-enter is /far/ too > easy to hit by > >accident. > > > >The plain reactor doesn't have any default at all; it finds > them however you > >tell it to find them (i.e. */project.xml for everything one > subdirectory > >below the current location, **/project.xml for anything any number of > >subdirectories below the current location). > > > >The multiproject wrapper around the reactor has a default as > described in my > >initial reply. > > > > > -----Original Message----- > > > From: Peter Bright [mailto:[EMAIL PROTECTED] > > > Sent: 26 March 2004 17:02 > > > To: 'Maven Users List' > > > Subject: RE: Quick reactor question > > > > > > > > > http://maven.apache.org/reference/plugins/multiproject/properties.html > > > > maven.multiproject.includes > > "Default value is */project.xml, that is all project.xml > > files one directory > > below the base directory " > > > > So I'm thinking you'll want to set it to **/project.xml instead. > > > > > -----Original Message----- > > > From: Andrew Bayer [mailto:[EMAIL PROTECTED] > > > Sent: 26 March 2004 17:03 > > > To: [EMAIL PROTECTED] > > > Subject: Quick reactor question > > > > > > > > > Hi - > > > I've got a sprawling and unpleasant source tree that > > > I'm moving into a > > > Maven-based build, using the reactor to call each of the many > > > sub-projects. > > > I just want to clarify exactly how the reactor finds > > > sub-projects - does it > > > only look in the first level of subdirectories below the > > > basedir or will it > > > look in the second, third, etc? If it doesn't look into the > > > deeper levels, > > > can I make it do so somehow? Here's a quick glance at our > > > directory structure: > > > > > > \ > > > \somedir1 > > > \somedir1\projectA > > > \somedir1\projectB > > > \somedir1\somedir2\projectC > > > \somedir1\somedir2\projectD > > > \projectE > > > > > > It's actually far more complex and ugly than that, with about > > > another 30 to > > > 40 projects at various levels, but that should give a sense > > > of what I'm > > > working with. Rearranging the source tree is a worst-case > > > option at best, > > > but if nothing else will work, I'll look into that option. Any > > > suggestions/pointers? > > > > > > A. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
