Yep, add it to JIRA. The solution I've used before is to have multiproject run install on any dependencies with the same groupId, but it is only a quickish solution. Reactor probably needs to take care of this itself - this is probably something to look at in 1.1
- Brett > -----Original Message----- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: Monday, 15 December 2003 7:14 AM > To: Maven Developers List; [EMAIL PROTECTED] > Subject: Re: multiproject:site and project interdependencies > (gather fails) > > > Sorry, wrong list!!! > > I'm cross-posting to the correct list... > > -john > > On Sun, 2003-12-14 at 14:59, John Casey wrote: > > Here is my scenario: I'm trying to run multiproject:site on a > > collection of mavenized projects in which some projects depend upon > > others. The multiproject plugin sorts them correctly in order of > > dependency, but then launches into some sort of gathering process > > (specified in the multiproject:site-init goal of the multiproject > > plugin)...which promptly breaks, since these projects have not yet > > been compiled. When I run multiproject:install, everything > is fine. By > > reading the multiproject plugin's plugin.jelly file a little bit, I > > assume the point is to create a collection of project objects for > > future use, to avoid having to re-collect them over and over. > > > > Is there any way to avoid this problem? Should I add a bug to JIRA > > and begin finding a solution? > > > > I appreciate any advice anyone can give. > > > > Regards, > > John Casey > > > > > > > --------------------------------------------------------------------- > > 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] >
