yeah...didn't read that closely enough. I'm still confused on what you mean by 'convenience builds'...is this something akin to an ejb-client as a secondary build, or what?
-j On Thu, 2004-03-18 at 15:01, Alex Karasulu wrote: > John, > > > > -----Original Message----- > > From: John Casey [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 18, 2004 2:52 PM > > > > If you have a project.xml at the base level but never extend from it, it > > should not restrict this use case... > > > > -john > > > > On Thu, 2004-03-18 at 14:45, Alex Karasulu wrote: > > > Hello, > > > > > > Is there a way to invoke the reactor without having a project.xml for > > the > > > top level directory. Basically can I just have a maven.xml to invoke > > the > > > reactor. The reason I ask this is because I have multiple levels that I > > > would like to start off a reactor build on. The problem is the > > restriction > > > on the levels of inheritance. Only one level is allowed so I don't want > > to > > > have the extra POM on those levels where I want builds to occur for > > > convenience. > > And how do recommend I prevent the reactor from picking up POMs at > these intermediate levels in the directory structure when the > reactor is invoked up at the topmost level? Do I just use the > exclude attribute to do that, or is there a better way? Will maven > ignore POMs if they duplicate builds of a proper subset of the component > projects scheduled for the reactor? > > Alex > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey [EMAIL PROTECTED] CommonJava Open Components Project http://www.commonjava.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
