2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>: > Sorry, but our priority is to ensure that all artifacts are built with the > same plugins and use the same artifact versions. In your model I have to > duplicate all the versions for your individual service parents. That's what > I call an anti-pattern. No, thanks, we've already bitten enough by that.
I am not sure if I properly got your point, but I also think that using version ranges and no proper dep. mgmt will lead to using different submodule version in the same project. We had that with Maven 1, and wasn't that one of the main reasons for Maven 2? The dep mgmt makes using dep. more strict - it allows you to exactly nail down one version all other sub modules are sharing among each other - if, in the rare case, that there is a sub project that does need to violate this rule and has to use an older / newer version of a dep., you may do so by overiding its version number. Not sure if I got it right, but imho that was Michaels point, using version ranges and so...
