>The design pattern I would recommend is one where the pom being imported >contains nothing but the managed dependencies, i.e. it defines a library >of related artifacts. You wouldn't use such a pom in any other way so I
>don't see this as a compatibility problem. But any poms that are consuming this other pom won't parse in <2.0.9. (Even when deployed) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
