It causes a cyclic dependency error in the reactor because the master
project dependencies are passed on to the child project. Thus the child
project ends up depending on itself. Maybe an alternative, althought I
haven't tried, is to take out the
<extend>${basedir}/../project.xml</extend> tag from the child project
POM. Even if this works I'm left without the benefits of POM inheritence
and stuck redefining all the attributes in the child project POM.Maven output... D:\gst-ipm>maven build:all ear __ __ | \/ |__ Jakarta _ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8 Starting the reactor (this may take a while)... BUILD FAILED Introducing edge will cause a Cycle. Total time: 6 seconds D:\gst-ipm> -john -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2003 4:13 PM To: Turbine Maven Users List Subject: RE: Multiple War Files (Architecture Question) John, what's stopping you from specifying the child project's war as a dependency? -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au "Frey, John (MED)" <[EMAIL PROTECTED]> wrote on 04/03/2003 08:05:26 AM: > Ok that's basically what I thought. The only issue with this structure > is that the reactor doesn't allow me to specify the child project war > as a dependency in the master project's POM (the whole transitive > dependency issue). Unfortunately this renders the ear plugin useless. > > -john > > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Monday, March 03, 2003 2:09 PM > To: Turbine Maven Users List > Subject: RE: Multiple War Files (Architecture Question) > > > On Mon, 2003-03-03 at 15:01, Frey, John (MED) wrote: > > Are you suggesting then that each separate project be built and > > stored > > > in CVS under its own module? Or is it better to keep them as child > > projects of a top level project module? The reactor doesn't really > > care however the latter seems better to me since the documentation set > > > is common to all three projects. > > I'm not suggesting any SCM specifics here. You may have your own > preferences for your SCM. For Plexus we are using CVS and we have a > module for the container proper and one for the components. But that's > still rather arbitrary. With the components module we just have a set > of directories > > > Also, What do I do if I need to deploy both wars as part of an ear? > > Do > > > I need a separate project for that too? What I'd like to see is... > > As part of your master project you could have some logic in your > maven.xml file that triggers the builds for those two projects > producing WARs and then package them together into an EAR. > > > Master project: > > If your master project is in the business of producing an EAR file > then yes, this logic would be part of the master project's maven.xml > file. That's my take anyway. > > > Project.ear > > | > > | > > Child project: > > commons-logic.jar > > | > > | > > Child project: > > admin-view.war > > | > > | > > Child project: > > root-view.war > > > > -john > > > > -----Original Message----- > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 03, 2003 1:36 PM > > To: Turbine Maven Users List > > Subject: Re: Multiple War Files (Architecture Question) > > > > > > On Mon, 2003-03-03 at 13:22, James Ward wrote: > > > Thanks for the response. > > > > > > I have a typical web app with an end user area and an admin area. > > > I was creating two different war files ( ROOT.war and admin.war ). > > > Since they both share the same business logic I thought they were > the > > > same project. If this is incorrect, should I also have a > > > different > > > projects for the business logic and each war file; then use the > > > reactor to pull them all together? Or should I have the admin stuff > > > > in the ROOT.war file? > > > > separate project: > > commons-logic.jar > > > > separate project: > > root-view.war > > > > separate project: > > admin-view.war > > > > If you have something in common then separate it out and build that > > separately. You may find that you need a third and fourth type of > > view. Then you make more, small comprehensible builds instead of > > globbing those additional views all in the same place. Doing so will > > definitely make things harder to understand. > > > > Having a separate build for your common elements clearly > > distinguishes > > > what is common and your views are clearly separated. Granted there > > are > > > still some quirks with the reactor, the reactor is your friend and > > will make your projects easier to understand. > > > > > > > Thanks. > > > > > > -James > > > > > > > > > On Mon, 2003-03-03 at 11:04, Kurt Schrader wrote: > > > > Each project should have produce one war file. > > > > What use case do you have where you need to produce more than > > > > one? > > > > > > > > -Kurt > > > > > > > > On 3 Mar 2003, James Ward wrote: > > > > > > > > > Hello Maven Friends, > > > > > So, I am in quite a quandary... It seems like Maven and other > > > > > apps (like XDoclet) do not support (without a bit of hacking) > > > > > multiple war files. I am very curious as to why this is. > Should > > > > > I only have 1 war file per project? That doesn't seem right, > > > > > so > > > > > > why are multiple war files per project not better supported? > When > > > > > > > should I use multiple war files and when shouldn't I? > > > > > > > > > > Thanks for you input. > > > > > > > > > > -James > > > > > > > > > > > > > > > -------------------------------------------------------------- > > > > > -- > > > > > -- > > > > > --- > > > > > 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] > > > > > > > > > > > > > ------------------------------------------------------------------ > > > -- > > > - > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > [EMAIL PROTECTED] > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational and > technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- 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]
