I guess I'd go back to my original comment, and provide a bare-bones project.xml at the base dir, just as a placeholder...then, that will free you up to write a base-level maven.xml/project.properties to manage the various builds via multiproject and/or straight reactor. Or am I missing something?
If anyone has a better method, please pipe up. I have something like this in some cases, and am currently using the following: - multiproject:install goal - base-level project.properties with the following properties: - maven.multiproject.includes=projects/*/project.xml (note ONE star) - project-level project.properties with something akin to the following: - maven.multiproject.type=ejb (only specified at all when EJB project) Then, within the maven.xml of the EJB projects, I kick off the build for the ejb-client sub-project (arranged underneath the EJB project dir structure). This way, even when I run a build straight from an EJB sub-project, it will still build the ejb-client. I don't know if this helps or not, but there you go. Oh, and BTW, since I'm using multiple EJB's in some projects, I reference a maven.xml-in-disguise which lives in the base-directory, named something like 'maven-ejb-goals.xml' via something akin to <core:import file="../../maven-ejb-goals.xml" inherit="true"/> in the top of the EJB-project maven.xml file. Hope it helps... -john On Thu, 2004-03-18 at 15:16, Alex Karasulu wrote: > > -----Original Message----- > > From: John Casey [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 18, 2004 3:08 PM > > To: Maven Users List > > Subject: RE: [reactor] Invoking reactor without a project.xml > > > > 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? > > Not exactly John - let me clarify by describing the whole situation. > Basically I have a directory structure like so: > > top server dir/ > frontend/ > subsystem/ > comp1/ > comp2/ > ... > backend/ > Same situation as the frontend > > I want to be able to build the entire server up at the top. If I want > I would like to build the front end or the backend only because of the > amount of time it takes for the build. Likewise we can extend the same > case to the subsystem level or to the component level. > > What is the best way for me to handle these 'convenience' builds at the > various levels using Maven? > > If the reactor facility did not rebuild every time but only when one > was necessary due to changes to the project or to one of its dependencies > this would not be an issue or is this possible some how and I don't know > it. > > Alex > > > 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] > > > > > --------------------------------------------------------------------- > 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]
