> I've set up a "bom" file that lists a set of dependencies that multiple > projects use. > > In a "consumer" project, I've set up a dependencyManagement stanza > listing this bom as a dependency/type = pom/scope = import. > > Now, in this same "comsumer" project, maven doesn't see those > dependencies. I've even tried listing the dependencies that exist in > the "bom" in the "consumer" project (minus version info) and it still > fails.
As far as I understand it, the import scope was only designed to import dependencyManagement. Thus, it will not actually ADD any dependencies to your project, merely help you manage versions etc by adding those in dependencyManagement from the imported POM to the dependencyManagement section of your current POM. It won't import from any sections in your pom other than dependencyManagement, so dependencies themselves are ignored. So, it sounds like your experiences mostly match what I would expect. I'm not using import scope yet myself for anything serious, so I can't really tell you about personal experiences, only what I've read and seen thus far myself. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
