You are definitly missing something :) For the eclipse part, you should run eclipse:eclipse from the root project to use project dependency instead of binary dependency (ie a module will directly use another module as its dependency instead of using the produced jar).
For the reactor part (the building of the parent project), you certainly have something wrong with your projects. Are all the version numbers up to date? Do you have any cyclic dependencies? If you really can't have it work, fill in a JIRA issue, but this *should* work. (and in my case, it is working, as in most cases). Denis. Wojciech Biela wrote: > > Hi > > I think I'm missing something, I hope I'm missing something, otherwise > this is a great joke .. > > When I have a project and multiple subprojects depending on eachother. > I update all of them and then when I build the master project, each > submodule crashes because it's dependencies are not up to date. I have > to go and manually "mvn install" each submodule that had changed and > only then I can properly build the whole thing from the master module > .... how can I make this more usable ??? > > the problem gets more irritating when I have the whole system under > eclipse and after update all submodules (as eclipse projects) light up > red .... > > -- > Wojtek Biela > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/have-to-manually-build-each-submodule--tf2140589.html#a5908698 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
