Hi, yes, you are right. My problem is indeed, that mvn install must be called everytime, when I change something in the module, another module depends on.
Some times, I use the command line (there its no problem). But most time, I use eclipse. I've searched for a tutorial for that problem, but the result doesn't really satisfy me. How do you handle that problem? Is there a best practise? best regards -------- Original-Nachricht -------- > Datum: Fri, 1 Oct 2010 21:35:58 -0400 > Von: Wendy Smoak <[email protected]> > An: Maven Users List <[email protected]> > Betreff: Re: Dependencies between modules of a multi module project > On Fri, Oct 1, 2010 at 8:08 PM, Jon Paynter <[email protected]> wrote: > > I suspect we are missing something in the way maven was designed to > work. > > How is multi-module development intended to work? > > You have it right. Maven will not go build a sibling module, it will > use what's in the local repository. > > Most IDEs are capable of watching for changes and re-compiling on the > fly so that you have the latest available. > > If you are working from the command line and want that behavior, you > need to build from the top. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
