You can create a pom in a higher directory to include them as modules, or use a combination of a ci server and an artifact repository to make sure they are already build and waiting in the artifact repository.
Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Wed, May 6, 2009 at 12:22 PM, Blackbird <panzrku...@yahoo.fr> wrote: > > Hi, > > I have an application composed of 10 Eclipse projects, which depend on each > other. One of them is a webapp and it depends on several Eclipse projects, > and some of these Eclipse projects depend on others, so the dependency tree > is quite complex. > > In good-old Eclipse build, I don't have to care about that dependencies > tree: as long as the necessary projects are specified in the "Required > projects on the build path" section, my webapp will build successfully in 1 > user task. > > In Maven even though the dependencies are defined in the POM, if the > required projects don't exist in the local repository, calling "mvn clean > install" for my webapp will fail. As a result, I have to "mvn install" every > single Maven project on the build path first. > > Is there a way of calling "mvn install" on projects if they don't exist in > the local repository? > -- > View this message in context: > http://www.nabble.com/automatically-calling-%22install%22-target-for-projects-which-are-not-in-the-repository-tp23403861p23403861.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
