On 8/9/06, Mike Perham <[EMAIL PROTECTED]> wrote:
Not exactly. We have a single parent POM per ear and don't share war/ejbs between ears, yes. But you can still do what you want with a dependencyManagement section in the parent to centralize the version numbers and just have each ear POM pull in its required ejbs. Or am I missing something?
Defining <dependencyManagement> in the parent does not seem to cover all the cases for me. A simplified scenario goes like this: * Parent POM declares a version for artifact A * Child POM declares (or inherits) a dependency on artifact B * Dependency B declares a dependency on artifact A with an explicit, but different, version number. It seems that the two dependencies on artifact A are at the same "level" (in the terms of the book's section on this) and therefore the behavior is undefined. Indeed, it seems to work for most of the dependencies with version conflicts, but not all of them ... and it is completely unclear to me at this point why the cases are different. mike Craig Jörg Schaible <[EMAIL PROTECTED]> wrote on 08/09/2006
11:46:10 AM: > > Unfortunately this pattern does only help if you build a single EAR. > For multiple EARs (we have so) and a lot of EJBs (not exclusivly > referenced), you cannot define the dependencies in a common parent, > since then you woud end up with all depednencies of all EJBs in > every EAR. So you use a dependencyManagement (we do) and you're left > with the already described problem - you cannot force transitive > dependencies toi the version defined in the management. >
