This extends beyond multiproject. Maven needs the ability to load a project without satisfying all it's dependencies.
This would allow the reactor to happily succeed as well. Let's *NOT* make it the default, instead, just a configurable property with good error messages. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ John Casey <[EMAIL PROTECTED]> wrote on 15/12/2003 06:59:02 AM: > 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]
