Please see my comments below: <[EMAIL PROTECTED]>Yep, you need to run a reactor'ed jar-install or multiproject:install/multiproject:install-snapshot</[EMAIL PROTECTED]>
<b.hartin>This is what we're trying to do, e.g. maven.xml contains a reactor tag which specifies to attain the "jar:install" goal for all project.xml files it finds. However, when running this for a project (projectA) like Steve described, reactor never runs because the build fails immediately. To reproduce our problem, set up two dummy projects, projectA and projectB. These are sibling projects, i.e. B is not a subproject of A. Make A dependent on B in A's project.xml file. Now create a maven.xml file for A and add a goal called "all" containing only the reactor tag as described above. When I run 'maven all' from within A's directory, it gives me the 'unsatisfied dependency' message. I would think it would have executed "jar:install" for B first. It doesn't seem to matter what goal you're trying to achieve when you execute 'maven [goalname]'. I tried setting up a goal for A which just printed something to the screen, and maven still fails because the dependency on B isn't satisfied. It seems that maven will _never_ run any goal for a project, including reactor, if a dependency for that project isn't satisfied. Is this correct?</b.hartin> Brian Hartin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2003 7:48 PM To: Maven Users List Subject: RE: Beginner's question about reactor "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] **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
