The reactor will do it automatically for you if you define a dependency to core in was and bea projects.
Arnaud > -----Message d'origine----- > De : Mark D. Hansen [mailto:[EMAIL PROTECTED] > Envoy� : jeudi 3 mars 2005 23:41 > � : Maven Users List > Objet : RE: breaking a PROJECT up into multiple Maven Projects > > Looks helpful. Do you know if its possible to define an > ordering on the projects, so that - in my case - if I were > to run maven -Dgoal=jar multiproject:goal, it would run > myproj-core FIRST, and then the other myproj-* ?? > > Thanks, > > Mark > > > -----Original Message----- > > From: Galder Zamarre�fffffffffff1o [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 03, 2005 3:45 PM > > To: Maven Users List > > Subject: Re: breaking a PROJECT up into multiple Maven Projects > > > > > > Have you had a look into the Maven Multiproject plugin? > > > > http://maven.apache.org/reference/plugins/multiproject/ > > > > --- "Mark D. Hansen" <[EMAIL PROTECTED]> wrote: > > > I have a big-ish project that want to structure as multiple maven > > > projects. I'm wondering is there is a standard "best > practice" way > > > to do this. Below are details of my PROJECT. > > > > > > PROJECT is a J2EE application. It has a core set of > functionality > > > that runs under any J2EE implementation. It also has components > > > that are tweeked for specifica J2EE implementations (e.g., > > > WebSphere, BEA, etc). > > > > > > I've broken it into these Maven projects: > > > myproj-core, myproj-was, myproj-bea. The directory > structure looks > > > like this: > > > > > > myproject > > > myproject/myproj-core > > > myproject/myproj-was > > > myproject/myproj-bea > > > > > > Obviously, one of the dependencies for myproj-was and > myproj-bea is > > > myproj-core. How do I set this up in Maven? For > example, is there > > > a way so that when I run "maven jar" on myproj-was, the > > > myproj-core.jar automatically gets rebuilt? And how do I put > > > myproj-core.jar on the myproj-was classpath? I have my > own simple > > > repository and I could put myproj-core.jar in the repository and > > > then list it as a dependency for myproj-was. But, when I make a > > > small change to myproj-core and rebuild the > myproj-core.jar, then I > > > have to keep updating the repository. This seems kludgy. > Is there > > > a better way? > > > > > > Thanks for any help on this. > > > > > > -- Mark > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > --------------------------------------------------------------------- > 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]
