"Steve Garcia" <[EMAIL PROTECTED]> wrote on 02/10/2003 07:33:08 AM:
> Yea you basically got it right. However I was under the impression that > when you specify the "include" and "exclude" tags of the maven:reactor tag > it would 1) first find all project.xml files according to the fileset and > exclude the ones that match your exclude pattern and 2) work out which > projects to compile first based on the project.xml dependencies. The reactor does what you tell it to do. It doesn't know about 'compiling' code. > Suppose I have a single maven project and it requires the Log4J jar file and > some jar file called "projectB-1.0.jar". All maven would do is try to > download the projectB artifact from the maven.repo.local, and if that failed > it would to go a remote repository. If that failed the compile goal fails. Yep, you need to run a reactor'ed jar-install or multiproject:install/multiproject:install-snapshot > I think what you want is for Maven to recognize that the "projectB-1.0.jar" > is actually an artifact that can be produced by some other maven project, > and have it find that project.xml and compile/jar:install that jar into the > maven.repo.local repository. How would maven know that projectB is an > artifact that can be produced on your system and not a normal one that can > be downloaded? At this point I'm not sure. I don't think that is in there. It sure isn't. If you tell reactor to do a 'clean', should it do the above, I don't think so. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
