On 10/3/05, Miks Rozenbergs <[EMAIL PROTECTED]> wrote: > And now comes the question -- do I understand correctly that Maven would > not support such a model? That in Maven's case the dependant source > project should be added to <dependencies> AND ALSO ALL Module POM's > (IMHO I will need several Module POM's, as one DLL is used in multiple > components)? Which means someone should MANUALLY resolve dependencies!
This doesn't sound right, but I'm afraid I'm not sure you are referring to by a module. In Maven terms, a module is a way for trigger multiple builds from a common root, which often but not necessarily corresponds to the inheritence hierachy. I think what you are assuming is that this is necessary so that you can build all of the dependencies in your tree, giving them all a common root. If you want to rebuild everything at once, this is true - but that defeats the purpose of the Maven repository. You should only need to rebuild the pieces of the system in development, and for those you need to select the latest version in your dependencies anyway. We have experimented with rebuilding dependencies from scratch, either through the reactor or by checking them out from the SCM. Both are possible, but only useful under clean room builds or such situations - not general development as it is too slow. I hope this clears it up. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
