On 24/09/2007, Ralph Goers <[EMAIL PROTECTED]> wrote: > Yes, you have to specify <scope>import</scope> for the import to happen. > The type also has to be a pom. Ideally when doing this projects would > create a bill of materials pom for others to use and then use the import > only in poms that they use to build with. Presumably, that project would > also import the bill of materials pom as well. At least, that was how > the use case was described to me by the folks who want it.
Was this approach actually agreed upon? Last I remember there was a brief discussion on the dev list. I'd have thought the proposal & vote approach should be taken for something as substantial as this before committing to both 2.0.x and 2.1. Also, I'd rather see 2.0.8 released before throwing more features in at the last minute. I'm not convinced that this new virtual scope is a good way forward. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
