Not entirely true. If you do compile it will get a handle to the classes in the dependencies target folder. Package will get a handle to the jar in the target folder.
The problem is sometimes this isn't enough for a plugin to do what it needs. So yes you really should just do install in a multimodule build and it will work. -----Original Message----- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Saturday, March 22, 2008 4:22 AM To: Maven Users List Subject: Re: Customizing Build order Yes. But even from parent pom, only mvn install or higher works, anything lower than install results in an error if the dependency project not in local repository otherwise if there takes an older version existing in local repository or remote. Regards, Amit On Fri, Mar 21, 2008 at 7:56 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > What you are asking for doesn't exist, but is covered by some proposals: > > http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode > http://jira.codehaus.org/browse/MNG-2576 > http://jira.codehaus.org/browse/MNG-1694 > > The reordering only happens when you build from a parent pom that > aggregates all your children. Otherwise, currently, you need to have the > dependencies installed in your repository. > > --Brian > > -----Original Message----- > From: amit kumar [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2008 9:32 AM > To: Maven Users List > Subject: Re: Customizing Build order > > How to list that dependency? I do have the dependency of A3 on B1 and > B2(in > the <dependency> tag as jar). But that doesn't seems to make Maven go to > build B1 and B2 when building A3 because I guess it looks in the > repository, > if not there it throws an error. > > If it has been working in this way, it would have been the solution. But > I > am not able to see that happening. > > Is there a different way of mentioning a project As' dependency on > another > projectB that would trigger the build of projectB as soon as it finds in > the > dependencies? of that project? > > > Regards, > Amit. > > On Wed, Mar 19, 2008 at 6:49 AM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > > > Maven starts with the ordering listed in the poms (A and its children, > > then B and its children, etc) unless there is a dependency. If it sees > a > > dependency, then it will automatically reorder by pushing down modules > > that have a dependency so they build after their dep. > > > > I'm wondering why the order matters if you don't have a dependency > > listed (I'm assuming you don't or it would be ordered already). > > > > -----Original Message----- > > From: amit kumar [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 18, 2008 4:42 AM > > To: Maven Users List > > Subject: Customizing Build order > > > > Hi, > > I have a multi-module project with the following structure. > > > > Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > In the Root's pom i have mentioned my modules as: > > <module>A</module> > > <module>B</module> > > > > Now is there a way that I can change the normal build order(which is) > > > > -Root > > -A > > -A1 > > -A2 > > -A3 > > -B > > -B1 > > -B2 > > -B3 > > -B4 > > > > > > to something like > > > > -Root > > -A > > -A1 > > -A2 > > -B > > -B1 > > -B2 > > -A3 > > -B4 > > > > It is actually a requirement. But I doubt that there is a possibility > > that > > the CVS structure itself is not competent enough then to handle > > inter-module > > dependencies. > > > > Any inputs? > > > > Thanks and regards, > > Amit Kumar > > > > --------------------------------------------------------------------- > > 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]
