Hmmm - I noticed that the "bom" project had all its dependencies listed as provided, removing that in the bom file and then in the consumer pom deciding what scope there fixed this.
-----Original Message----- From: EJ Ciramella [mailto:[email protected]] Sent: Friday, January 30, 2009 4:46 PM To: [email protected] Subject: <scope>import</scope> Hello m2list - I'm struggling to get the <scope>import</scope> bit to work and I can't tell if it's something I'm doing wrong or how this actually works. 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. How is this supposed to go together? The documentation of this feature is to the Nth degree and a bit confusing. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
